Update to Vert.x 4.5.8 and Netty 4.1.110

[cescoffier]

• bump Mutiny Bindings to 3.13.0
• bump Quarkus HTTP to 5.3.0
• update Netty SSL released substitutions

Netty 4.1.111 causes a problem in gRPC. It seems to be a frame size issue. Need to be investigated.

[gsmet]

Please check your IDE settings. A few star imports crawled in.

comment addressed

[geoand]

cc @franz1981 who I know wants to try the new AdaptivePoolingAllocator

[cescoffier]

We would need to investigate the gRPC failure. My quick analysis indicates that it's a frame size issue. The response exceeded the default frame size.

[geoand]

Is that reflection test thing that was disabled testing a feature that is really obscure?

[cescoffier]

Yeah the reflection service from gRPC (which has nothing to do with Java reflection) is a way to discover gRPc services.

However, it might fails because there is something else going on. We need to investigate.

[cescoffier]

@franz1981 @geoand @vietj So, the gRPC issue comes from an incompatibility between grpc java and NEtty 4.1.111. PRevious versions of Netty work :-(. Need to see which commit can causes such a problem.

We may have to stay on 4.1.110 for now.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 88c2895.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

---

Flaky tests - Develocity

⚙️ JVM Tests - JDK 21

📦 integration-tests/reactive-messaging-kafka

✖ io.quarkus.it.kafka.KafkaConnectorTest.testFruits - History

• Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <5> within 10 seconds. - org.awaitility.core.ConditionTimeoutException

org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in io.quarkus.it.kafka.KafkaConnectorTest expected: <6> but was: <5> within 10 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:31)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:1006)
	at org.awaitility.core.ConditionFactory.untilAsserted(ConditionFactory.java:790)
	at io.quarkus.it.kafka.KafkaConnectorTest.testFruits(KafkaConnectorTest.java:63)
	at java.base/java.lang.reflect.Method.invoke(Method.java:580)

[gastaldi]

The commit message seems misleading, given that Netty is no longer updated?

[gsmet]

@gastaldi Netty is updated but just to 4.1.110.

[gsmet]

@cescoffier is it something we want to shoe in 3.12?

[gastaldi]

Ah doh, I missed the Netty bump, nvm

[cescoffier]

@gsmet no :-)

[franz1981]

FYI netty/netty#12919 (comment)

[vietj]

interesting, thanks

…

On Thu, Jun 13, 2024 at 4:15 PM Clement Escoffier ***@***.***> wrote: @franz1981 <https://github.com/franz1981> @geoand <https://github.com/geoand> @vietj <https://github.com/vietj> So, the gRPC issue comes from an incompatibility between grpc java and NEtty 4.1.111. PRevious versions of Netty work :-(. Need to see which commit can causes such a problem. We may have to stay on 4.1.110 for now. — Reply to this email directly, view it on GitHub <#41155 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABXDCSOSBX7NK5IRA5FGO3ZHGSOLAVCNFSM6AAAAABJGA5ZPOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVHAYDCOBYHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[franz1981]

@cescoffier so final verdict grpc/grpc-java#11284 (comment)

[vietj]

we need to check if there is anything TBD in vertx

…

On Mon, Jun 17, 2024 at 8:44 AM Francesco Nigro ***@***.***> wrote: @cescoffier so final verdict grpc/grpc-java#11284 (comment) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>