-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix(core): Catch beforeSendSpan callback throws
#22836
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
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
00a6196
fix(core): Don't let a throwing `beforeSendSpan` callback escape into…
Lms24 00053fb
guard all beforeSendSpan callback invocations
Lms24 84c658b
fix build, add tests
Lms24 b344093
lint
Lms24 282d43b
cleanup
Lms24 955b8b2
avoid let, inline showSpanDropWarning
Lms24 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 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
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
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
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
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
Oops, something went wrong.
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.
Unmodified root span still merged
Low Severity
When
beforeSendSpanthrows or returns null for the root span,applyBeforeSendSpanCallbackcorrectly hands back the original span JSON, but the caller alwaysmerges the convert round-trip into the transaction. Previously a null return left the event untouched. Becausemergereplacescontexts.tracewholesale and the converters apply defaults, the “unmodified” fallback can still alter the event.Reviewed by Cursor Bugbot for commit 8745c98. Configure here.
Uh oh!
There was an error while loading. Please reload this page.
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.
yeah I'm willing to take this risk. mutating the originally passed in json is not something we directly recommend but we should still expected. It might even be advantageous here: If users scrub first, and then decide to return
null, the scrubbing still gets applied if they mutate in-place. This should be fine to change, especially in v11. I'm not planning on backporting this PR anyway.