Skip to content
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

Bump to Vert.x 4.3.1 and Netty 4.1.78 #26294

Merged
merged 2 commits into from Jun 25, 2022

Conversation

cescoffier
Copy link
Member

@cescoffier cescoffier commented Jun 22, 2022

This new combination is tricky. It imposes to have brotli4j available in the classpath as, because of the new HTTP compression feature from vert.x, it does now have a hard dependency on brotli4j. While in JVM mode, everything is fine, native compilation fails if not there. We have tried a few things to avoid the dependency, but we are hitting oracle/graal#4652.

@quarkus-bot quarkus-bot bot added area/dependencies Pull requests that update a dependency file area/vertx area/amazon-lambda labels Jun 22, 2022
@quarkus-bot

This comment has been minimized.

@quarkus-bot

This comment has been minimized.

This new combination is tricky. It imposes to have brotli4j available in the classpath as, because of the new HTTP compression feature from vert.x, it does now have a hard dependency on brotli4j. While in JVM mode, everything is fine, native compilation fails if not there. We have tried a few things to avoid the dependency, but we are hitting oracle/graal#4652.
@cescoffier
Copy link
Member Author

@Sanne @DavideD - looks like we will be able to update to Vert.x 4.3.1. Do you have any concerns on your side?

@DavideD
Copy link
Contributor

DavideD commented Jun 24, 2022

On the current main branch of Hibernate Reactive we are already using 4.3.1. It shouldn't be a problem for us.

@Sanne
Copy link
Member

Sanne commented Jun 24, 2022

@cescoffier great to hear :) and no concerns, it all seems under control 💯

@Sanne
Copy link
Member

Sanne commented Jun 24, 2022

@cescoffier regarding brotli: I'm aware of that graalvm limitation as I've hit similar issues in the past; FYI there are possible workarounds but aren't "pretty". I'd say it's totally fine to have the dependency around - or does it cause any particular issue (other than the extra disk space) ?

@cescoffier
Copy link
Member Author

@Sanne yes, that's the only issue. It even gets eliminated during the native compilation.

@cescoffier cescoffier merged commit d1371fc into quarkusio:main Jun 25, 2022
@quarkus-bot quarkus-bot bot added this to the 2.11 - main milestone Jun 25, 2022
@cescoffier cescoffier deleted the vertx-4.3.1-take-2 branch June 25, 2022 06:12
michalvavrik added a commit to michalvavrik/beefy-scenarios that referenced this pull request Jun 27, 2022
Two days ago Vert.X were [bumped to 4.3.1](quarkusio/quarkus#26294) that caused errors in CI daily runs. According to the [4.3 release notes](https://vertx.io/blog/whats-new-in-vert-x-4-3/#vertx-web) the handler order matters, I also found similar issue [reported here](vert-x3/vertx-web#2182]. Security policy handler `CorsHandler` should be registered after the logging handler.
@michalvavrik
Copy link
Contributor

Hello @cescoffier , upgrade from Vert.X 4.2.7 to 4.3.1 also bring some important changes (f.e. Vet.X Web handlers order is now validated), please see 4.3 release notes. Could you please add "noteworthy" label and add details about the change to https://github.com/quarkusio/quarkus/wiki/Migration-Guide-2.11 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants