Conversation
jkmassel
force-pushed
the
update/sentry-sdk
branch
3 times, most recently
from
9d133a3 to
7844cd3
Compare
- Updates the Sentry SDK without causing any breaking changes - Fixes up tests to be compatible with the new SDK (some weren’t particularly useful) - Adds a switch to force-enable Sentry events in debug builds (`-force-crash-logging=1`)
jkmassel
force-pushed
the
update/sentry-sdk
branch
from
7844cd3 to
406c7d4
Compare
1 task
Contributor
|
@jkmassel I'm curious if you've tried working with their newer SDK since May 😄 |
Contributor
Author
|
Closing in favour of #166 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
-force-crash-logging=1)