You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The documentation for process_request correctly says that the first value should be an HTTPStatus; however, this example passes a plain int instead.
Expected result: An exception is thrown or displayed on the console. (Or ideally, this particular case should work correctly, since IntEnum and integer are mostly interchangeable.)
Actual result: The exception is swallowed by # Last-ditch attempt to avoid leaking connections on errors and the connection is summarily closed with no message to client or console.
Requesting that the last-ditch handler report errors to the console, possibly with a message indicating how this could be suppressed.
The text was updated successfully, but these errors were encountered:
Ahh cool, that solves this particular issue. It may still be possible to cause other types of errors that will silently abort connections though. Is there any other way to write the handler that will result in the same last-ditch exception handler being triggered?
The documentation for process_request correctly says that the first value should be an HTTPStatus; however, this example passes a plain int instead.
Expected result: An exception is thrown or displayed on the console. (Or ideally, this particular case should work correctly, since IntEnum and integer are mostly interchangeable.)
Actual result: The exception is swallowed by
# Last-ditch attempt to avoid leaking connections on errors
and the connection is summarily closed with no message to client or console.Requesting that the last-ditch handler report errors to the console, possibly with a message indicating how this could be suppressed.
The text was updated successfully, but these errors were encountered: