Send Sentry reports on uncaught throws/exits #447
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fix getsentry#446 Previously PlugCapture would only catch exceptions. If there was an uncaught exit or throw, this would be ignored and Plug/Phoenix would end up send a 500 Internal Server Error to the clients with no notification to Sentry.
|
Thank you so much, this is perfect! 💖 |
|
Can this be released? I just noticed this issue and I see that the latest |
|
@cheerfulstoic yep, thank you for the reminder and sorry for the delay. I've just pushed version 8.0.5 to hex. |
|
🎉 ❤️ Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #446
Previously PlugCapture would only catch exceptions. If there was an uncaught exit or throw, this would be ignored and Plug/Phoenix would end up send a 500 Internal Server Error to the clients with no notification to Sentry.