notice_notifier: fix confusing error message #525
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
Addresses #524 (Error Airbrake: performance notifier closed causes deadlock) A user reported that he saw the following message in the logs: > Airbrake::Error (attempted to build deadlock; recursive locking with closed Airbrake instance) Because exceptions are stringified, the error message can get very confusing. In issue #524 the user thought that there's a deadlock in airbrake-ruby (me too, to be honest), but when I took a closer look, it turned out that we print the exception we're building as a string. I changed the message, so it's more obvious what's going on.
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.
Addresses #524 (Error Airbrake: performance notifier closed causes deadlock)
A user reported that he saw the following message in the logs:
Because exceptions are stringified, the error message can get very confusing. In
issue #524 the user thought that there's a deadlock in airbrake-ruby (me too,
to be honest), but when I took a closer look, it turned out that we print the
exception we're building as a string.
I changed the message, so it's more obvious what's going on.