You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Our instrumentation ChannelHandlers are always inserted after the original one. That means if someone calls ChannelPipeline#removeLast() it'll remove our handler, but leave the original HTTP client/server one in the pipeline.
What did you expect to see?
Probably we should always remove both handlers (the original HTTP one & the instrumentation one) at a time?
maybe we should check the handler type when removeLast is called. If the handler type is ourhandler, we should call removeLast again to remove the handler user actually want.
Describe the bug
Our instrumentation
ChannelHandler
s are always inserted after the original one. That means if someone callsChannelPipeline#removeLast()
it'll remove our handler, but leave the original HTTP client/server one in the pipeline.What did you expect to see?
Probably we should always remove both handlers (the original HTTP one & the instrumentation one) at a time?
Additional context
#4053 (comment)
The text was updated successfully, but these errors were encountered: