fix(otel): Copy active span on scope clone #4878
Merged
+18
−0
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.
📜 Description
When cloning a
Scopewe now copy theactiveSpanover.💡 Motivation and Context
Not copying it means we don't know what the current span is, causing
Sentry.getSpan()to returnnullafter current scope has been forked.This showed up, when implementing feature flags on spans where the span created by OpenTelemetry auto instrumentation was not returned by
Sentry.getSpan()andaddFeatureFlagdid not write to that span.💚 How did you test it?
📝 Checklist
sendDefaultPIIis enabled.🔮 Next steps