-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Drain HttpResponse
in tests
#5852
Conversation
Motivation: In Armeria CI, we saw Netty leak reports from kubernetes-client CI tests. After investigating, I found out that some of the tests did not consume `HttpResponse`. As a result, some `ByteBuf`s were not subscribed to and remained in the Publisher's internal buffer. Modifications: - Fixed to call `AsyncBody.consume()` where it was not called before. Result: No more leaks in CI builds.
@ikhoon : Could you please run |
I've done. |
Quality Gate passedIssues Measures |
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
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, thx!
Description
In Armeria CI, we saw Netty leak reports from kubernetes-client CI tests. After investigating, I found out that some of the tests did not consume
HttpResponse
. As a result,ByteBuf
s were not subscribed to and remained in the Publisher's internal buffer.I fixed to call
AsyncBody.consume()
in tests where it was not called before.Type of change
test, version modification, documentation, etc.)
Checklist