-
-
Notifications
You must be signed in to change notification settings - Fork 334
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
feat: Close session for unhandled error #3091
Merged
Merged
Changes from 5 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
69c1637
feat: Close session for unhandled error
brustolin a187d02
Update SentryHubTests.swift
brustolin 7a33aa9
suggestions
brustolin 078d671
Format code
getsentry-bot 2ce0cbe
Update SentryHubTests.swift
brustolin edca2c6
Update SentryHub.m
brustolin aab4503
Format code
getsentry-bot 99177cf
Update SentryHubTests.swift
brustolin 1c55ca4
Apply suggestions from code review
brustolin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
h
: That's not how we safely end and start a new session. I think we should call the following instead.As we also do in the session tracker
sentry-cocoa/Sources/Sentry/SentrySessionTracker.m
Lines 173 to 174 in 60dd0f5
Or am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm missing something, but this is what I get:
currentSession
is a clone of the current session, If a callself endSessionWithTimestamp
this will not endcurrentSession
.[hub endSession]
the session is immediately captured, but here, the session was being sent in the same envelope.startSession
the last session is also capture, which would duplicate the captureThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, then what I proposed doesn't seem correct. Your solution definitely needs a lock with
@synchronized(_sessionLock)
when creating the new session, you need to handle_errorsBeforeSession
, you need to handle the edge case when there is no releaseName, and you need to store the new session and also capture the new session. Similar to whatstartSession
does. I think it would be better to maybe refacrotstartSession
so you can also use it here.Furthermore, I think it would make sense to not increment the session error when the event is unhandled. We should just mark it as crashed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please, take a look at the new approach.