-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Uncaught exception handling improvement #969
Comments
Thanks for the feedback. Just to clarify, given the last two points are existing behavior, the remaining task is to change the log level to ERROR on any uncaught exceptions? I think that seems reasonable to change. |
Yes, just wanted to be very clear how all the other behaviors are great and I wouldn't want to lose them. |
Oops, I guess my reply was actually wrong. I am also suggesting that the ERROR level log message is also generated when DEBUG is not enabled. I went to make the code change and realized my mistake. I'll submit a PR in a second so you can see what I'm thinking. Hopefully this change is also acceptable. |
Here's the code diff to be clear, and hopefully to encourage progress on this issue ;-) |
Hi @dmulter - just changed this into a PR for the chalice project. This is a pretty big deal for me for operational monitoring too. |
Merged with #1144 |
Currently uncaught exceptions log a DEBUG level message (includes stack trace) and return this in the body of the HTTP error response if DEBUG is enabled. An
InternalServerError
is returned without any logging if DEBUG is not enabled.Please consider the following alternate behavior:
InternalServerError
without stack trace if DEBUG is not enabled (existing behavior).See this section of code:
chalice/chalice/app.py
Line 738 in 947eb8f
The text was updated successfully, but these errors were encountered: