-
Notifications
You must be signed in to change notification settings - Fork 784
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
Fix regression introduced in #1126 (brave headers propagation) #1206
Fix regression introduced in #1126 (brave headers propagation) #1206
Conversation
…tion) Before spring-cloud#1126, the headers were eagerly set in `TraceExchangeFilterFunction#filter`. After it, the side effect was moved to lazy `MonoWebClientTrace#subscribe`. However, we have everything to instrument the request in `filter`, and it can be done eagerly.
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.
Test?
That's exactly what we're discussing with @marcingrzejszczak right now in Slack :D Will check shortly, I like writing tests 👍 |
FYI the manual testing was done with the repro project from #1199 |
@spencergibb ok, writing a test took less than 15 minutes 🎉 |
Codecov Report
@@ Coverage Diff @@
## master #1206 +/- ##
============================================
- Coverage 69.95% 69.94% -0.01%
Complexity 753 753
============================================
Files 141 141
Lines 3521 3520 -1
Branches 383 383
============================================
- Hits 2463 2462 -1
Misses 845 845
Partials 213 213
Continue to review full report at Codecov.
|
Before #1126, the headers were eagerly set in
TraceExchangeFilterFunction#filter
. After it, the side effect wasmoved to lazy
MonoWebClientTrace#subscribe
.However, we have everything to instrument the request in
filter
,and it can be done eagerly.
This should fix #1199