Potencialy bad bug? (server exit unexpectably)

[op183]

Following the basic tutorial (first step only, with "Hello" response) https://docs.hummingbird.codes/2.0/tutorials/todos, I've built debug and release versions.

running
release 1% ./App --hostname 0.0.0.0 --port 8080

and from the second shell
2% curl -i http://192.168.0.183:8080
curl: (52) Empty reply from server // stderr

the app exit with
1% ....
2025-02-10T16:04:09+0100 info Todos : [HummingbirdCore] Server started and listening on 0.0.0.0:8080
2025-02-10T16:04:23+0100 error Todos : [HummingbirdCore] Waiting on child channel: NIOFcntlFailedError()
Error: ServiceGroupError: errorCode: A service has finished unexpectedly., file: ServiceLifecycle/ServiceGroup.swift, line: 337

I expected the same response as for
% curl -i http://localhost:8080
HTTP/1.1 200 OK
Content-Type: text/plain; charset=utf-8
Content-Length: 6
Date: Mon, 10 Feb 2025 15:12:04 GMT
Server: Todos

Hello!%

The response and App (server) trace are as expected using the app's debug binary.               

Any idea? (macOS Sequoia 15.3) (swift-driver version: 1.115.1 Apple Swift version 6.0.3 (swiftlang-6.0.3.1.10 clang-1600.0.30.1)
Target: x86_64-apple-macosx15.0)

[adam-fowler]

Are you able to do this on a vanilla app without all the content added during the tutorial? I couldn't replicate myself. I'll try with the tutorial tomorrow.

[adam-fowler]

There is no chance you clicked on a dialog box saying don't accept incoming network messages. This will come up on the first connection if you run with bind address 0.0.0.0

[op183]

If you ask me about some firewall restrictions, that is not the case; all works as accepted if running debug binary. With the release binary the packets reach the App, and the App is finished if the request goes to ip: 192.168.0.x (ip address of the computer in the local network, en0). It works if the request goes to ip: 127.0.0.1 (loopback, lo)

It seems the initial trouble goes from

....
try? Posix.close(descriptor: fd) // don't care about failure here
if error.errnoCode == EINVAL {
// Darwin seems to sometimes do this despite the docs claiming it can't happen
throw NIOFcntlFailedError()
}
....

In swift-nio/Sources/NIOPosix/SocketProtocols.swift, extension BaseSocketProtocol, func ignoreSIGPIPE(descriptor fd: CInt)

This is source of the error reported by the App as [HummingbirdCore] Waiting on child channel: NIOFcntlFailedError()

I am not able to see where this function is called from and why, if, in my case, NIO should use Network.framework!!! In debug binary this function is never called :-)

[adam-fowler]

If you want to use Network framework initialise your Application with the following parameter

let application = Application(
    ...
    eventLoopGroupProvider: .shared(NIOTSEventLoopGroup.singleton)
)

This passes in a transport services event loop group to Application.

[adam-fowler]

If you ask me about some firewall restrictions, that is not the case; all works as accepted if running debug binary. With the release binary the packets reach the App, and the App is finished if the request goes to ip: 192.168.0.x (ip address of the computer in the local network, en0). It works if the request goes to ip: 127.0.0.1 (loopback, lo)

I wasn't thinking about firewall restrictions. I was more wondering about app sandboxing. I can replicate your issue with exactly the same error messages by clicking "Deny" when the dialog asking Do you want the application "App" to accept incoming network connections? appears. After that it won't allow me to connect using the IP address of the computer.

I found if I completely delete the application binary (using swift package clean) its sandbox is reset and I can rebuild it and run it fine

[op183]

If you ask me about some firewall restrictions, that is not the case; all works as accepted if running debug binary. With the release binary the packets reach the App, and the App is finished if the request goes to ip: 192.168.0.x (ip address of the computer in the local network, en0). It works if the request goes to ip: 127.0.0.1 (loopback, lo)

I wasn't thinking about firewall restrictions. I was more wondering about app sandboxing. I can replicate your issue with exactly the same error messages by clicking "Deny" when the dialog asking Do you want the application "App" to accept incoming network connections? appears. After that it won't allow me to connect using the IP address of the computer.

I found if I completely delete the application binary (using swift package clean) its sandbox is reset and I can rebuild it and run it fine

Will try it ... still, should the App exit with error in such a case?

[op183]

If you ask me about some firewall restrictions, that is not the case; all works as accepted if running debug binary. With the release binary the packets reach the App, and the App is finished if the request goes to ip: 192.168.0.x (ip address of the computer in the local network, en0). It works if the request goes to ip: 127.0.0.1 (loopback, lo)

I wasn't thinking about firewall restrictions. I was more wondering about app sandboxing. I can replicate your issue with exactly the same error messages by clicking "Deny" when the dialog asking Do you want the application "App" to accept incoming network connections? appears. After that it won't allow me to connect using the IP address of the computer.

I found if I completely delete the application binary (using swift package clean) its sandbox is reset and I can rebuild it and run it fine

1. I've tried, no luck. I did "Hello World" with Hummingbird v1 and it works as expected, with no problems... It should be somewhere between heaven and earth

2. Applications, programs, and services that can accept incoming connections are listed in Firewall>Options. !!! I did not find the application there!!! So I add the application manually. It was on the list. I tried to run it and it was immediately removed from the list!

3. I turned off the firewall and everything started working immediately. I enabled the firewall and IT WORKS AS EXPECTED.

Sorry to disturb you. Thank you for your patience and support!!

[op183]

If you want to use Network framework initialise your Application with the following parameter

let application = Application(
    ...
    eventLoopGroupProvider: .shared(NIOTSEventLoopGroup.singleton)
)

This passes in a transport services event loop group to Application.

This is the key! Now the App doesn't exit, even the incomming connetions are blocked by the firewall. THX!!!!!