Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(12279)

Issue 66540043: Log context after the exception in default_exception_handler()

Can't Edit
Can't Publish+Mail
Start Review
Created:
10 years, 2 months ago by haypo_gmail
Modified:
10 years, 2 months ago
Reviewers:
yselivanov
Visibility:
Public.

Description

Log context after the exception in default_exception_handler()

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+104 lines, -65 lines) Patch
M asyncio/base_events.py View 2 chunks +8 lines, -5 lines 1 comment Download
M asyncio/futures.py View 2 chunks +4 lines, -5 lines 0 comments Download
M asyncio/test_utils.py View 1 chunk +1 line, -1 line 0 comments Download
M tests/test_base_events.py View 6 chunks +41 lines, -27 lines 0 comments Download
M tests/test_selector_events.py View 2 chunks +24 lines, -12 lines 0 comments Download
M tests/test_unix_events.py View 2 chunks +26 lines, -15 lines 0 comments Download

Messages

Total messages: 1
yselivanov
10 years, 2 months ago (2014-02-20 16:00:04 UTC) #1
Victor, to be honest, I don't think this is an issue.

https://codereview.appspot.com/66540043/diff/1/asyncio/base_events.py
File asyncio/base_events.py (right):

https://codereview.appspot.com/66540043/diff/1/asyncio/base_events.py#newcode677
asyncio/base_events.py:677: logger.error('\n'.join(log_lines))
Absolutely no!

Exception object *must* go to the logger routines. Lots of code relies on it,
just one example: error monitoring services like airbrake or newrelic install
their own LoggingHandlers to intercept exceptions and report them. They format
tracebacks and exception chains themselves.
Sign in to reply to this message.

Powered by Google App Engine
RSS Feeds Recent Issues | This issue
This is Rietveld f62528b