-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Fix assertDefaultThreadContext enumerating allowed headers #86262
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
Conversation
Default thread context should has headers from a finite set or be empty. The allowed headers are the ones that we want to "follow the request" so that we can log them. Previously the assertDefaultThreadContext was trying to enumerate combinations of allowed headers. Any combination with these headers is allowed, so we should simplify this method.
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Hi @pgomulka, I've created a changelog YAML for you. |
the bug highlighted itself after #68649 was merged. observe a failure:
|
…arch into fix_assert_default_tc
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.
much cleaner check. LGTM
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.
LGTM
…6262) Default thread context should has headers from a finite set or be empty. The allowed headers are the ones that we want to "follow the request" so that we can log them. Previously the assertDefaultThreadContext was trying to enumerate combinations of allowed headers. Any combination with these headers is allowed, so we should simplify this method.
💔 Backport failed
You can use sqren/backport to manually backport by running |
…6262) Default thread context should has headers from a finite set or be empty. The allowed headers are the ones that we want to "follow the request" so that we can log them. Previously the assertDefaultThreadContext was trying to enumerate combinations of allowed headers. Any combination with these headers is allowed, so we should simplify this method.
…86262) (#86271) Default thread context should has headers from a finite set or be empty. The allowed headers are the ones that we want to "follow the request" so that we can log them. Previously the assertDefaultThreadContext was trying to enumerate combinations of allowed headers. Any combination with these headers is allowed, so we should simplify this method.
Default thread context should has headers from a finite set or be empty.
The allowed headers are the ones that we want to "follow the request" so
that we can log them.
Previously the assertDefaultThreadContext was trying to enumerate combinations
of allowed headers.
Any combination with these headers is allowed, so we should simplify this method.
gradle check
?