Skip to content
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

Report response status when there is no response #1125

Merged
merged 1 commit into from
Jun 28, 2024

Conversation

tombruijn
Copy link
Member

When there is no response object given to the EventHandler's on_finish callback, we can expect an unhandled error has occurred.

When have also received an exception in the on_error callback, report the response status as 500. This solution is not perfect. It may actually be another response status if something else above the EventHandler handles the exception. A setup we don't recommend.

Part of #329

When there is no response object given to the EventHandler's `on_finish`
callback, we can expect an unhandled error has occurred.

When have also received an exception in the `on_error` callback, report
the response status as 500. This solution is not perfect. It may
actually be another response status if something else above the
EventHandler handles the exception. A setup we don't recommend.
@tombruijn tombruijn force-pushed the report-error-response-status branch from 7076077 to 6e67999 Compare June 28, 2024 06:46
@tombruijn tombruijn merged commit 0230ab4 into main Jun 28, 2024
16 checks passed
@tombruijn tombruijn deleted the report-error-response-status branch July 10, 2024 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants