Re: [PR] Test Netty 4.2.0.Final [pekko]

2025-04-14 Thread via GitHub
ferenc-csaky commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2803761694 > @ferenc-csaky wdyt , we plan to upgrade to netty 4.2.0.final in next version, Will flink upgrade to Netty 4.2.x too? Sorry for the late answer, AFAIK there is no push ATM to do

Re: [PR] Test Netty 4.2.0.Final [pekko]

2025-04-06 Thread via GitHub
He-Pin commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2781379857 @pjfanning Yes, we need some abstraction to do that, currently, it's bound to NioSocket, the Netty 4.2 is pretty cool about separate the iohandler with eventloop, I think that can be done mo

Re: [PR] Test Netty 4.2.0.Final [pekko]

2025-04-06 Thread via GitHub
mkurz commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2781369533 I agree. Just upgrading the dependency is definitely enough for now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use t

Re: [PR] Test Netty 4.2.0.Final [pekko]

2025-04-06 Thread via GitHub
pjfanning commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2781344348 @He-Pin @mkurz I had a quick look at Pekko code and it doesn't immediately look like we use the Netty abstractions that now support io_uring. I may have missed something. I would prefer t

Re: [PR] Test Netty 4.2.0.Final [pekko]

2025-04-06 Thread via GitHub
He-Pin commented on PR #1794: URL: https://github.com/apache/pekko/pull/1794#issuecomment-2781312080 @ferenc-csaky wdyt , we plan to upgrade to netty 4.2.0.final in next version, Will flink upgrade to Netty 4.2.x too? -- This is an automated message from the Apache Git Service. To respond