-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
fix(tracing): ignore the xhr/fetch response if its request is not being tracked #4428
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
5 commits
Select commit
Hold shift + click to select a range
e0137ef
fix(tracing): ignore the xhr response if its request is not being tra…
datbth c2e870c
chore(tracing): fix test
datbth d788c70
chore(tracing): refactor
datbth 3993dd3
fix(tracing): ignore the fetch response if its request is not being t…
datbth ccecb71
chore(tracing): fix test
datbth 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -359,7 +359,7 @@ describe('Hub', () => { | |
// TODO the way we dig out the headers to test them doesn't work on Node < 10 | ||
testOnlyIfNodeVersionAtLeast(10)( | ||
'should propagate positive sampling decision to child transactions in XHR header', | ||
() => { | ||
async () => { | ||
const hub = new Hub( | ||
new BrowserClient({ | ||
dsn: 'https://[email protected]/1121', | ||
|
@@ -375,12 +375,12 @@ describe('Hub', () => { | |
}); | ||
|
||
const request = new XMLHttpRequest(); | ||
request.open('GET', '/chase-partners'); | ||
|
||
// mock a response having been received successfully (we have to do it in this roundabout way because readyState | ||
// is readonly and changing it doesn't trigger a readystatechange event) | ||
Object.defineProperty(request, 'readyState', { value: 4 }); | ||
request.dispatchEvent(new Event('readystatechange')); | ||
await new Promise(resolve => { | ||
request.timeout = 1; | ||
request.onloadend = request.ontimeout = resolve; | ||
request.open('GET', '/chase-partners'); | ||
request.send(''); | ||
}); | ||
|
||
// this looks weird, it's true, but it's really just `request.impl.flag.requestHeaders` - it's just that the | ||
// `impl` key is a symbol rather than a string, and therefore needs to be referred to by reference rather than | ||
|
@@ -401,7 +401,7 @@ describe('Hub', () => { | |
// TODO the way we dig out the headers to test them doesn't work on Node < 10 | ||
testOnlyIfNodeVersionAtLeast(10)( | ||
'should propagate negative sampling decision to child transactions in XHR header', | ||
() => { | ||
async () => { | ||
const hub = new Hub( | ||
new BrowserClient({ | ||
dsn: 'https://[email protected]/1121', | ||
|
@@ -417,12 +417,12 @@ describe('Hub', () => { | |
}); | ||
|
||
const request = new XMLHttpRequest(); | ||
request.open('GET', '/chase-partners'); | ||
|
||
// mock a response having been received successfully (we have to do it in this roundabout way because readyState | ||
// is readonly and changing it doesn't trigger a readystatechange event) | ||
Object.defineProperty(request, 'readyState', { value: 4 }); | ||
request.dispatchEvent(new Event('readystatechange')); | ||
await new Promise(resolve => { | ||
request.timeout = 1; | ||
request.onloadend = request.ontimeout = resolve; | ||
request.open('GET', '/chase-partners'); | ||
request.send(''); | ||
}); | ||
|
||
// this looks weird, it's true, but it's really just `request.impl.flag.requestHeaders` - it's just that the | ||
// `impl` key is a symbol rather than a string, and therefore needs to be referred to by reference rather than | ||
|
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.
we probably want this logic to be like:
This is also more bundle size efficient
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.
hi, thanks for looking into this.
I have refactored into using the
spanId
variable as suggested.But I'm using eager-return style because it modifies less codes and I also believe multiple nesting levels is less readable. Not sure if it's significant to the bundle size?
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.
Well it's two
return
keywords rather than one (both of which can't be minified), but yeah the impact is probably minimal. We can leave it like this!