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

[fix] Ensure fatal panics are notified #77

Merged
merged 2 commits into from
Oct 5, 2018
Merged

Conversation

kinbiko
Copy link
Contributor

@kinbiko kinbiko commented Sep 21, 2018

Due to a bug in the existing notifier.NotifySync method, we end up
using the notifier's config value to determine whether to send
synchronously or async. In the case of a fatal panic (i.e not
AutoNotified or Recover-ed) it still got sent asynchronously.
This change ensures that it does get sent synchronously.

Tested by putting a panic immediately after the Bugsnag configuration, and seeing if it got reported.

Due to a bug in the existing `notifier.NotifySync` method, we end up
using the notifier's config value to determine whether to send
synchronously or async. In the case of a fatal panic (i.e not
`AutoNotified` or `Recover`-ed) it still got sent asynchronously.
This change ensures that it does get sent synchronously.
kattrali
kattrali previously approved these changes Oct 2, 2018
@kattrali kattrali merged commit 3f5889f into master Oct 5, 2018
@kattrali kattrali deleted the send-fatal-panics-sync branch October 5, 2018 21:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants