-
-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Handle Logger.exception() outside "except" block #635
Conversation
src/structlog/processors.py
Outdated
if exc_info: | ||
if exc_info != (None, None, None): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this was the actual bug, right? because a negative result from _figure_out_exc_info isn't falsey
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, more or less. The (None, None, None)
case was handled elsewhere (surprisingly, from a typing perspective ;-)), but it only worked for the default exception formatter.
src/structlog/processors.py
Outdated
_figure_out_exc_info(exc_info) | ||
) | ||
exc_info = _figure_out_exc_info(event_dict.pop("exc_info", None)) | ||
if exc_info != (None, None, None): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like this would pass any None
/Falsy exc_info in the event dict into the formatter. Is this expected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changed it to if exc_info and exc_info != (None, None, None)
. This should work.
Not happy though, that exc_info
can be literally anything. I will take a look if this can somehow be changed/improved.
assert {"exception": "MISSING"} == format_exc_info( | ||
None, None, {"exc_info": ei} | ||
) | ||
assert {} == format_exc_info(None, None, {"exc_info": ei}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this okay for you, @hynek ? The format_exc_info()
handled the (None, None, None)
(even though its signature suggested that exc_info: ExcInfo
) and returned {"excepiton": "MISSING"}
.
Now, (None, None, None)
will no longer be passed to it and thus there will no longer be a MISSING
.
The main problem of the function is that *v* can really be anything (depending on what the users) do and the annotated return type did not properly match it (e.g., if *v* was "0", the return value would be "0"). The function now rigorously checks the user input and either returns the desired result (an exc info tuple) or None. This makes it easier and safer to use this function.
I think that 0c02f29 really fixes the problem in the right way. I added a longer description to the commit to explain why. Let me know, what you think :) |
close on the wish of the author due to lack of feedback from OP |
Fixes: #634
Summary
Pull Request Check List
main
branch – use a separate branch!api.py
.docs/api.rst
by hand.versionadded
,versionchanged
, ordeprecated
directives..rst
and.md
files is written using semantic newlines.