-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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(instrumentation): Fix false double leading slashes in transaction names #80124
fix(instrumentation): Fix false double leading slashes in transaction names #80124
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
1a7aed1
to
16f6e8a
Compare
❌ 7 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
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.
This PR should fix this for real: getsentry/sentry-javascript#14821
But this seems like a good interim fix
@malwilley oh nice, I didn't see that! Since that PR's the proper fix, and this has already been broken for an eternity, I don't think this interim fix is really worthwhile, I'm just gonna close it 👍🏻 |
See comment in details. Prevents errors and transaction events with names like
"//dashboards/:dashboardId"
caused by a bad interaction between React Router 6 instrumentation in the SDK and our shimming setup.I'm not sure if other kinds of telemetry (Profiles, Replays, breadcrumbs) also need a fix, but it didn't seem like it.