-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Use Netty 4.1.116.Final or 4.1.117.Final #45655
Comments
/cc @cescoffier (netty), @franz1981 (netty), @geoand (knative), @iocanel (knative), @jponge (netty) |
If we do update, it should be to 4.1.117 |
We will have to see how Vertx works with this new version. Vertx 4.5.12 should be released next week. |
@geoand thanks! I now see the matching tag: https://github.com/netty/netty/tree/netty-4.1.117.Final The GH repo was just hinting the 4.1.116 Final as last release |
@cescoffier Last week there was already a version bump of |
Yes, but know we need to wait for this release and then deal with the potential native compilation issues. The Vertx release is expected this week. So expect some work on that next week. |
Describe the bug
With a 3.15.3 based installation, we are seeing: netty/netty#14479
Which is introduced in Netty
4.1.115.Final
and fixed in4.1.116.Final
.Can this be included into a 3.15.4 release of quarkus?
Our issue is captured here, in this comment: knative-extensions/eventing-kafka-broker#4214 (comment)
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
No response
Quarkus version or git rev
No response
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response
The text was updated successfully, but these errors were encountered: