Johannes Weiss

NonBlockingFileIO.read(...) don't error if more than 4 GiB is requested

4

A `ByteBuffer` can never hold more than 4 GiB of data. But the `NonBlockingFileIO.read(...)` functions don't complain if more than that is requested. They should error saying that this request...

NIOLoopBound has bad error messages

4

``` NIOCore/NIOLoopBound.swift:47: Precondition failed ``` is all I get :|. I'd have expected some more information. Particularly: - what was wrong (wrong thread, maybe even expected and actual thread names)...

ClientBootstrap.resolver is hard to use for single-use resolvers

3

Some resolvers (like NIO's internal GAIResolver) are use-exactly-once objects. They work only if used once (not 0 times, not twice). ClientBootstrap.resolver is hard to use with those objects because one...

MultiThreadedEventLoopGroup: allow users to specify the thread name pattern

3

Right now, MTELG's thread name pattern is always `NIO-ELT-x-#y`. The `NIO-ELT-` part should be configurable by the user. And `NIOSingletons`'s ELG's (once https://github.com/apple/swift-nio/pull/2471 is in) should set that to something...

Document the suggested way to get an EventLoopGroup

13

In the past, NIO and other libraries carried the flawed (#2142) `*EventLoopGroupProvider` pattern. There were two primary concerns: 1. The easiest way to use other libraries was wasteful (`.createNew`) 2....

deprecate NIOEventLoopGroupProvider (#2142)

5

### Motivation: `NIOEventLoopGroupProvider.createNew` was probably never a good idea because it creates shutdown issues for any library that uses it. Given that we now have singleton (#2471) `EventLoopGroup`s, we can...

I hit this assertion https://github.com/apple/swift-nio/blob/324bc65a28323660fad8a36a7a37f0c2c78eeb9a/Sources/NIOPosix/BaseSocketChannel.swift#L1077 when running the NIO tests in a tight sandbox. Output ``` Test Suite 'All tests' started at 2023-07-11 05:46:11.149. Test Suite 'swift-nioPackageTests.xctest' started at 2023-07-11...

NIO's Resolver interface pretty much forces thread hops for external Resolvers

3

https://github.com/apple/swift-nio/blob/5768317b704288e172b2dc927e7927f4c16843be/Sources/NIOPosix/Resolver.swift#L32 NIO's resolver interface doesn't tell the resolver what EventLoop the returned future should ideally be coming from. That means that a normal resolver will likely return futures of a...

CI is running on Kernel version 3.10, that is now a _decade_ old

2

### Expected behavior CI running on a kernel that's somewhat recent, I would've assume maybe something within the last 3 years. ### Actual behavior CI running on a 10-year old...