Johannes Weiss

request.body.drain calls out whilst user is still processing the previous callout

3

Generally in SwiftNIO and I reckon most/all futures based systems, when programming a function that looks like func provider(_ consumer: (Item) -> EventLoopFuture) Then the programmer should expect that `provider`...

running Vapor tests in parallel fails

3

If you run ``` docker run -it --rm -w "$PWD" -v "$PWD:$PWD" swift:5.3 swift test --enable-test-discovery --parallel --num-workers 1 ``` in a vapor checkout, your tests won't succeed. You'll see...

flaky tests HTTPClientTests.testClientProxyPlaintext & HTTPClientTests.testClientProxyTLS

3

``` $ swift test Fetching https://github.com/apple/swift-nio.git Fetching https://github.com/apple/swift-nio-ssl.git Fetching https://github.com/apple/swift-nio-http2.git Fetching https://github.com/apple/swift-nio-extras.git Fetching https://github.com/apple/swift-log.git Completed resolution in 5.60s Cloning https://github.com/apple/swift-nio-ssl.git Resolving https://github.com/apple/swift-nio-ssl.git at 2.4.0 Cloning https://github.com/apple/swift-log.git Resolving https://github.com/apple/swift-log.git at master...

``` Last login: Wed Nov 13 20:30:14 on ttys018 johannes:~ $ cd devel/scrip -bash: cd: devel/scrip: No such file or directory -1- johannes:~ $ cd devel/scripts -bash: cd: devel/scripts: No...

In SwiftNIO it's generally a good idea that on `errorCaught`, the `Channel` should be closed to prevent leaking network connections that are in some error states. In Vapor this should...

ByteBufferView: implement most Collection/Sequence customisation points

6

`ByteBufferView` is a `Collection` of `UInt8` which "views" into a `ByteBuffer`. Right now, we basically only implement the `subscript` which vends individual bytes. That's good enough to implement `Collection`/`Sequence` (and...

Enable Documentation building on the Swift Package Index

1

Swift Package Index just launched the awesome feature which [generates docs](https://blog.swiftpackageindex.com/posts/auto-generating-auto-hosting-and-auto-updating-docc-documentation) for any package. SwiftNIO should enable this by adding the required `.spm.yml` etc.

See https://swiftpackageindex.com/apple/swift-nio/builds ``` /Applications/Xcode-13.3.0.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -emit-module -experimental-skip-non-inlinable-function-bodies-without-types ${cwd}/Sources/NIOMulticastChat/main.swift -target x86_64-apple-macos10.10 -enable-objc-interop -sdk /Applications/Xcode-13.3.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -I ${cwd}/.derivedData/Build/Products/Debug -I /Applications/Xcode-13.3.0.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib -F ${cwd}/.derivedData/Build/Products/Debug/PackageFrameworks -F ${cwd}/.derivedData/Build/Products/Debug/PackageFrameworks -F ${cwd}/.derivedData/Build/Products/Debug/PackageFrameworks -F ${cwd}/.derivedData/Build/Products/Debug/PackageFrameworks -F ${cwd}/.derivedData/Build/Products/Debug/PackageFrameworks -F ${cwd}/.derivedData/Build/Products/Debug/PackageFrameworks -F...

ecosystem issue: EventLoopGroupProvider and the 'similar create or share ELG' pattern

13

The NIO ecosystem suffers from one composability issue: `EventLoopGroupProvider` and similar constructs. The issue is that taking `EventLoopGroupProvider` (or similar) means that a library can either own or not own...