Skip to content

Conversation

@briankrznarich
Copy link
Contributor

@briankrznarich briankrznarich commented Oct 24, 2025

Just noticed that I've had this change locally on disk for a year. If you look at the logic for ConnListener.Close() , it calls cl.listener.Close(), which in turn causes listener.Accept() calls in related goroutines to return with errors. These errors are logged to stderr before the routines end.

These errors should not be emitted when the connection is manually/cleanly closed. The existing call to close(cl.quit) has no impact on preventing these errors.

Especially when using go-ios as a library where connections are dynamically opened and closed, these errors are quite undesirable.

…onnection

After manually closing a forward connection, several threads only exit after a call to accept() fails due to the the underlying resource being cleanly closed.  This is not an error, and these errors can distract from a clean shutdown.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant