You can click on the Google or Yahoo buttons to sign-in with these identity providers,
or you just type your identity uri and click on the little login button.
reformulate this ticket to talk about cache handling issue on multi-instances setup?
auc, up on this patch?
I'm tempted to bail out.
What is the status of this ticket ? why can't we just raise an exception ?
raising here is just VERBOTEN
but Why ?
because it's called cw_attr_value, not cw_attr_value_may_raise
its not called cw_attr_value_silently_ignore_error_please neither
This is (as you already know) heavily used in views and it is not permissible vor views to crash on users just because of a glitch in the multi-source system (or some cache handling issue).
This happen in non multisource environment too.
really ? In which condition ? Beside with a broken database, in which case returning null makes sense, I fail to see what could trigger this.
I got the error during test. With a thread leaking after db restore.
the error was obscure enought to make me loose a couple hour
Ticket #2122238 - latest update on 2012/05/23, created on 2011/12/13 by Aurelien Campeas