-
Notifications
You must be signed in to change notification settings - Fork 181
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
Update Netty 4.1.77 -> 4.1.78 #2250
Conversation
// We manage flushes at ST level and don't want netty to flush the preface & settings only. Instead, we write | ||
// headers or entire message and flush them all together. Netty changed the default flush behavior starting from | ||
// 4.1.78.Final. For context, see https://github.com/netty/netty/pull/12349. | ||
flushPreface(false); |
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.
For users which run older Netty with ServiceTalk I assume that this change will have no impact since the prior default was to not flush the preface, correct?
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.
Correct. You have a good point about older versions of netty. I've switched to MethodHandle
to avoid breaking users who may depend on older netty.
MethodHandle flushPreface; | ||
try { | ||
// Find a new method that exists only in Netty starting from 4.1.78.Final: | ||
flushPreface = MethodHandles.publicLookup() |
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.
should we create an issue to eventually just use the API directly?
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.
Sure, #2251
No description provided.