Repository navigation
fix(tracing): keep propagated tags intact across baggage headers #1919
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
lets-order-some-fries
wants to merge
1
commit into
langfuse:main
Choose a base branch
from
lets-order-some-fries:fix/baggage-tags-separator
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
["red","blue"]is parsed as two tags here. The downstream span recordsredandblueinstead of the original tag, making trace tags unreliable for this valid value.Knowledge Base Used: OpenTelemetry propagation and export
Prompt To Fix With AI
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.
Good catch on the edge case. A single tag whose text is itself a JSON array is ambiguous on the wire: the AI gateway's
parse_tagsreads["red","blue"]as two tags as well, and the JS SDK's comma split already breaks that tag apart today. I kept the reader consistent with the gateway, but I'm happy to narrow it if you'd prefer.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.
That鈥檚 a fair clarification. Given that the wire format is already ambiguous and the gateway鈥檚
parse_tagsapplies the same interpretation, keeping the reader aligned with the gateway is the least surprising behavior. The JS SDK鈥檚 comma-delimited format also cannot preserve a tag containing commas, so narrowing only the Python reader would not restore round-trip fidelity. I鈥檓 withdrawing this edge-case finding; no change is needed here.Tip: You can customize Greptile's behavior for this repo with
.greptile/rules.mdand.greptile/config.json.