fix: remove bugsnag api key message #4144
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
without an API key bugsnag displays the following warning: "not delivering sessions due to an invalid api_key" It is something that new people often get worried about. This PR sends that warning to dev/null chaskiq/chaskiq#251 (comment)
elasticspoon
force-pushed
the
fix-bugsnag-message
branch
from
ee29240 to
15208c1
Compare
|
@elasticspoon: Your PR |
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.
Without an API key bugsnag displays the following warning:
It is something that new people often get worried about and is very annoying when using irb for debugging. This PR sends that warning to
dev/nullif an API key is not provided.Solution take from here
Type of change