[4.x] Set weight for WebClientTracing
provider greater than that for WebClientSecurity
provider
#8274
+63
−1
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.
Description
Likely/possibly resolves #8192
Assign an explicit weight to
WebClientTracingProvider
that is greater than the weight forWebClientSecurityProvider
(which is the default). This makes sure that Helidon invokesWebClientTracing#handle
beforeWebClientSecurity#handle
. The latter depends on the request context containing span information which is set byWebClientTracing#handle
.With no explicit weight set, the order of execution is indeterminate and could create the kind of failure noted in the issue.
(I tried creating a simple test but, because without explicit weighting the order is indeterminate, the test passed even without the fix because the order just happened to be the order that works: tracing, then security. So the PR contains no test.)
Documentation
bug fix; no doc impact