-
Notifications
You must be signed in to change notification settings - Fork 791
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
Add Netty instrumentation handlers after matched handler rather than at end of pipeline. #2100
Add Netty instrumentation handlers after matched handler rather than at end of pipeline. #2100
Conversation
Warning this PR will pass, but testLatestDeps is still broken with the error message in the description so should only be merged after manual verification. Looked here but couldn't find anything that matches that class weirdly |
the "org.springframework.core" part is matching, and we need to add exception for this class, e.g.
|
…-instrumentation into support-latest-webflux
Thanks @trask - fixed and confirmed locally testLatestDeps works |
@@ -30,6 +32,8 @@ test { | |||
inputs.files(tasks.findByPath(':javaagent:shadowJar').outputs.files) | |||
maxParallelForks = 2 | |||
|
|||
timeout = Duration.ofMinutes(30) |
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.
Had to raise timeout since seems to fail on CI at 15 min too nowadays
While I think it's generally a bug, in practice we can't be sure that the pipeline will propagate events we need through to the end because who knows what the user's handlers will be doing. We can be sure that Netty's default handlers do though, so
addAfter
is safer thanaddLast
.Fixes #2098
This is close, tests pass but I get this mysterious error. @trask do you know the magic?