)]}'
{"aodh/api/hooks.py":[{"author":{"_account_id":1669,"name":"Julien Danjou","display_name":"jd","email":"julien@danjou.info","username":"jdanjou"},"change_message_id":"eda8d819260e61e621d1ee44d31e35afb143afd0","unresolved":false,"context_lines":[{"line_number":49,"context_line":"        # If it has we need to get it info the thread-safe WSGI"},{"line_number":50,"context_line":"        # environ to be used by the ParsableErrorMiddleware."},{"line_number":51,"context_line":"        if hasattr(state.response, \u0027translatable_error\u0027):"},{"line_number":52,"context_line":"            state.request.environ[\u0027translatable_error\u0027] \u003d ("},{"line_number":53,"context_line":"                state.response.translatable_error)"}],"source_content_type":"text/x-python","patch_set":1,"id":"1a4dcd0f_6ec72996","line":52,"updated":"2015-08-07 14:34:59.000000000","message":"If we do that, why don\u0027t we just put the error in state.request.environ directly in the code?","commit_id":"f9a9b3ea81518c71c261fdf8c9ca7dba48d398a9"},{"author":{"_account_id":11564,"name":"Chris Dent","email":"cdent@anticdent.org","username":"chdent"},"change_message_id":"b9a764addcfd58faa58b5d843a45cd2231e4fa06","unresolved":false,"context_lines":[{"line_number":49,"context_line":"        # If it has we need to get it info the thread-safe WSGI"},{"line_number":50,"context_line":"        # environ to be used by the ParsableErrorMiddleware."},{"line_number":51,"context_line":"        if hasattr(state.response, \u0027translatable_error\u0027):"},{"line_number":52,"context_line":"            state.request.environ[\u0027translatable_error\u0027] \u003d ("},{"line_number":53,"context_line":"                state.response.translatable_error)"}],"source_content_type":"text/x-python","patch_set":1,"id":"1a4dcd0f_ee333912","line":52,"in_reply_to":"1a4dcd0f_6ec72996","updated":"2015-08-07 14:41:53.000000000","message":"Yeah, unfortunately I tried that. The problem is that in ClientSideError you cannot access pecan.request.environ without causing an error because we are outside the __call__ context of the WSGI application. If we were in a situation where we were able to let exceptions bubble up directly to the ParsableErrorMiddleware we could just take their test directly.\n\nThat\u0027s the very large change that I decided not to do mentioned in the commit message.","commit_id":"f9a9b3ea81518c71c261fdf8c9ca7dba48d398a9"}]}