Tracing header propagation fixes #3005
Merged
Conversation
This file contains 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
- Instead of converting incoming `=` characters to `_`, convert incoming `~` characters - Then, if there are any incoming `=` characters, convert them to `~`
TonyCTHsu
approved these changes
Jul 27, 2023
Merged
Merged
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.
This PR addresses all the nonconformities that
ddtracehad regarding Header propagation.These were caught by our system-tests, at: DataDog/system-tests#1437.
After these changes, that PR successfully passes all critical Ruby tests.
There are other tests that are currently ignored in system-tests for Ruby, but those are outside the scope of this PR and can be discussed on a separate channel.