fix: update otel integration to properly activate span context for lazy RPCs such as reads & writes pt.2 #3277
Conversation
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
…zy RPCs such as reads & writes The initial attempt at this could leak scope and result in new spans being nested incorrectly. This approach attempts to be less clever, but bounds all scopes so there isn't any leaking. Followup to #3255
cojenco
approved these changes
Sep 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The initial attempt at this could leak scope and result in new spans being nested incorrectly. This approach attempts to be less clever, but bounds all scopes so there isn't any leaking.
Leaked spans in v2.56.0
Fixed spans after this PR
Followup to #3255