-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix(core): Rethrow caught promise rejections in startSpan
, startSpanManual
, trace
#9958
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
size-limit report 📦
|
Lms24
force-pushed
the
lms/fix-startspan-throws
branch
from
December 21, 2023 20:26
3a3bf53
to
722683d
Compare
Lms24
commented
Dec 21, 2023
...ges/browser-integration-tests/suites/public-api/startSpan/error-async-throw-ii/template.html
Outdated
Show resolved
Hide resolved
lforst
approved these changes
Dec 22, 2023
Lms24
force-pushed
the
lms/fix-startspan-throws
branch
from
December 22, 2023 08:58
19c82d2
to
c474988
Compare
mydea
reviewed
Dec 22, 2023
packages/browser-integration-tests/suites/public-api/startSpan/error-async-reject/test.ts
Outdated
Show resolved
Hide resolved
mydea
reviewed
Dec 22, 2023
...ges/browser-integration-tests/suites/public-api/startSpan/error-async-throw-ii/template.html
Outdated
Show resolved
Hide resolved
mydea
reviewed
Dec 22, 2023
packages/browser-integration-tests/suites/public-api/startSpan/error-async-throw/template.html
Outdated
Show resolved
Hide resolved
mydea
approved these changes
Dec 22, 2023
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.
Very good find & fix! I think this should be good.
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.
This severely messed with my brain today..
Seems like our previous implementation of
startSpan
et.al. assumed that because we were "cloning" the original promise, unhandled promise rejections would still bubble up to the globalonunhandledrejection
handler so that Sentry would catch the error.However, we tried investigating this and found out that our "cloning" mechanism didn't work correctly and because we already added a rejection handler, the promise rejection would not always make it to the global handler.
After adding multiple integration tests, I further narrowed the buggy behaviour down to a rather special case:
As we can see in the example, the
startSpan
call is notawait
ed which for some reason will lead to the SDK not catching the error. Unless, we apply the fix in this PR.This PR removes this cloning mechanism in favour of directly attaching a rejection handler to the promise. In this handler, we rethrow the error which should trigger the global handlers.