-
-
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
ref(tracing): Extract propagation context from meta tags #8430
Conversation
size-limit report 📦
|
This PR address the tracing tests stuff: #8431 |
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.
lgtm!
@@ -214,7 +214,7 @@ export function shouldAttachHeaders(url: string, tracePropagationTargets: (strin | |||
* | |||
* @returns Span if a span was created, otherwise void. | |||
*/ | |||
function fetchCallback( | |||
export function fetchCallback( |
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.
l: why is this change necessary?
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.
It was because this was actually being imported by tests:
import { fetchCallback, instrumentOutgoingRequests, shouldAttachHeaders, xhrCallback } from '../../src/browser/request'; |
@@ -364,7 +364,7 @@ export function addTracingHeadersToFetchRequest( | |||
* | |||
* @returns Span if a span was created, otherwise void. | |||
*/ | |||
function xhrCallback( | |||
export function xhrCallback( |
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.
l: same question here
Building on top of #8430, this PR makes a quick fix to make sure we are running unit tests for `@sentry-internal/eslint-plugin`, `@sentry-internal/tracing`, and `@sentry-internal/replay-worker`. This was found not to be running before because we had a blanket `--ignore @sentry-internal/*` when making lerna run tests.
ref #8352
This PR makes sure the
BrowserTracing
integration updates the propagation context based on meta tags. To ensure we don't keep the same propagation context, we continuously update it every time a route change should happen (navigation).Note that we have a bunch of test changes here. This is because we actually weren't running any of the tracing tests in CI because of a blanket ignore we use (this logic is all in
@sentry-internal/tracing
. I'm fixing this in a follow up PR.sentry-javascript/package.json
Lines 28 to 29 in e02c27f