-
-
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(core): Ensure non-sampled spans are NonRecordingSpans #14955
base: develop
Are you sure you want to change the base?
Conversation
size-limit report 📦
|
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.
Thanks, good catch!
81cedd8
to
a011992
Compare
❌ 8 Tests Failed:
View the top 3 failed tests by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Otherwise, parts of the DSC will be missing - we try to make it as complete as we can. Since the span cannot be updated anyhow (e.g. the name cannot be changed), we can safely freeze this at this time. Extracted out of #14955
…tion` (#14959) Extracted this out of #14955 We used to rely on implied stuff here quite a bit, which breaks if we start returning non recording spans. Honestly this just surfaces that this is not really ideal as it is 😬 We already pass the client around there everywhere, so this PR updates this so we keep the active idle span as non-enumerable prop on the client, ensuring this is consistent and "pure".
ce4c3ca
to
984a0de
Compare
ecc9230
to
6bac717
Compare
Noticed that we were still using a regular SentrySpan for unsampled spans, instead of NonRecordingSpans. This should be more "consistent" now.