-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[Test] Allow trace.id in default thread context. #76089
Merged
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
A new trace.id header is added by elastic#74210. It is handled almost the same way as x-opaque-id. Specifically, it gets passed into default thread context. This means the existing assertion should expect it in addition to x-opaque-id.
ywangd
added
>test
Issues or PRs that are addressing/adding tests
:Core/Infra/Logging
Log management and logging utilities
v8.0.0
v7.15.0
labels
Aug 4, 2021
Pinging @elastic/es-core-infra (Team:Core/Infra) |
pgomulka
approved these changes
Aug 4, 2021
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.
great find. I totally forgot about this.
Did this highlight itself in any tests?
LGTM
No, I noticed it when doing ad-hoc manual testings. |
ywangd
added
the
auto-backport
Automatically create backport pull requests when merged
label
Aug 5, 2021
elasticsearchmachine
pushed a commit
to elasticsearchmachine/elasticsearch
that referenced
this pull request
Aug 5, 2021
A new trace.id header is added by elastic#74210. It is handled almost the same way as x-opaque-id. Specifically, it gets passed into default thread context. This means the existing assertion should expect it in addition to x-opaque-id.
💚 Backport successful
|
ywangd
pushed a commit
that referenced
this pull request
Aug 5, 2021
A new trace.id header is added by #74210. It is handled almost the same way as x-opaque-id. Specifically, it gets passed into default thread context. This means the existing assertion should expect it in addition to x-opaque-id.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
auto-backport
Automatically create backport pull requests when merged
:Core/Infra/Logging
Log management and logging utilities
Team:Core/Infra
Meta label for core/infra team
>test
Issues or PRs that are addressing/adding tests
v7.15.0
v8.0.0-alpha2
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.
A new trace.id header is added by #74210. It is handled almost the same
way as x-opaque-id. Specifically, it gets passed into default thread
context. This means the existing assertion should expect it in addition
to x-opaque-id.
Relates: #74210