Francesco Nigro

@kant2002 the `Requests/sec` metric includes the time required to receive responses as well or is just considering the "test duration time"?

Any news on this @trustin ?

@trustin > Are you asking this because you're using Armeria or the outcome of this issue could be useful to Netty as well? slightly_smiling_face The latter: I've very few free...

There are some test failures related missing `sendFile` support that I'm working around by forcing `supportsFileRegion` to return `false` with IoUring on `ConnectionBase::sendFile`: ```java public final ChannelFuture sendFile(RandomAccessFile raf, long...

I've fixed https://github.com/eclipse-vertx/vert.x/issues/4163#issuecomment-964126155 with https://github.com/franz1981/vert.x/commit/4eafe9ff3fdaad1ab79768b02465aaacadd1f1eb

Just FYI this is the last run: ``` Results : Failed tests: Http1xTest>HttpTest.testListenDomainSocketAddress:144->HttpTestBase.startServer:93->HttpTestBase.startServer:118->AsyncTestBase.awaitLatch:598->AsyncTestBase.awaitLatch:602->AsyncTestBase.assertTrue:378 null Http2ClientTest.lambda$testNetSocketConnect$198:1428->AsyncTestBase.assertEquals:241 expected: but was: Http2ServerTest.lambda$testNetSocketConnect$250:2251->AsyncTestBase.assertEquals:241 expected: but was: Http2Test>HttpTest.testListenDomainSocketAddress:144->HttpTestBase.startServer:93->HttpTestBase.startServer:118->AsyncTestBase.awaitLatch:598->AsyncTestBase.awaitLatch:602->AsyncTestBase.assertTrue:378 null Http2Test>HttpTest.lambda$testServerConnectionHandlerClose$573:3625->AsyncTestBase.fail:414 null NetTest.testListenDomainSocketAddress:1896->startServer:3843->startServer:3855->AsyncTestBase.awaitLatch:598->AsyncTestBase.awaitLatch:602->AsyncTestBase.assertTrue:378 null NetTest.access$2400:77->AsyncTestBase.assertEquals:360 expected:...

I should add some check re domain socket support on JUnit tests

It seems that `ubuntu-latest` is hitting https://github.com/netty/netty-incubator-transport-io_uring/blob/07bf47cef7436d392623fef34eecf0cd0f9b88bb/README.md#i-tried-to-use-io_uring-but-got-javalangruntimeexception-failed-to-create-io_uring-ring-fd-cannot-allocate-memory Meaning that: - we should find a way to change `mlock` limits on it - we run it through qemu or docker our...

Following up: https://github.community/t/how-to-raise-ulimits-on-the-github-runner/181781

@vietj time for some action :P https://github.com/netty/netty-incubator-transport-io_uring/pull/159/checks It seems now we can make use of our CI to run io_uring tests yeeeeeeeeeee