New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Assign ErrPipeListenerClosed to net.ErrClosed #242
Conversation
This error used to just be a `errors.New` with the text exactly matching the "use of closed network connection" that you'd get from the Go stdlib. Now that that error was exported as `net.ErrClosed` in Go 1.16 we should be able to swap to this safely, and anyone who relied on checking the string explicitly should still be fine. Signed-off-by: Daniel Canter <dcanter@microsoft.com>
CI's using Go 1.15.5 and that's the reason for the fail, will look in a little. Edit: Our tests didn't specify a go-version, fixed. |
Add in a ^1.17.0 go-version for the actions/setup-go@v2 action. This was set for our build step but not for the step that runs all of the unit tests. Signed-off-by: Daniel Canter <dcanter@microsoft.com>
@thaJeztah I could only see here where moby was making use of this, and it seems like the usage would continue working. Maybe our comment was out of date There's these two spots that check the error text but they're both using tcp/http conns, so not really relevant. |
fyi @katiewasnothere @ambarve as I think we'd talked about this before |
@katiewasnothere @ambarve Anybody able to give this a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This error used to just be a
errors.New
with the text exactly matching the "use of closed network connection" that you'd get from the Go stdlib. Now that that error was exported asnet.ErrClosed
in Go 1.16 we shouldbe able to swap to this safely.