Skip to content

Conversation

@fgid
Copy link

@fgid fgid commented Jun 4, 2016

When using go 1.6.1, after adding some debug, I find:
ne.Err.Error() is "read: connection reset by peer"
but syscall.ECONNRESET.Error() is "connection reset by peer"

They are not equal, so I make this fix to work around.

Since 0.9.7 build is also built with go 1.6.1, I think it is the root cause causing issue #445 #454

When using go 1.6.1, after adding some debug, I find:
ne.Err.Error() is "read: connection reset by peer"
but syscall.ECONNRESET.Error() is "connection reset by peer"

They are not equal, so I make this fix to work around.

Since 0.9.7 build is also built with go 1.6.1, I think it is the root cause causing cyfdecyf#445 cyfdecyf#454
@cyfdecyf cyfdecyf merged commit 7e2bf73 into cyfdecyf:develop Jun 11, 2016
@cyfdecyf
Copy link
Owner

Thank you for the PR.

@cyfdecyf
Copy link
Owner

@Smallthing I guess the same fix should also work for Windows, but I don't have any Windows machines or VMs to test it.

@fgggid
Copy link

fgggid commented Jun 23, 2016

@Smallthing You can try my PR #465 for windows

Laisky pushed a commit to Laisky/cow that referenced this pull request Oct 25, 2022
Fix conn reset handling for go 1.6.1
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.

4 participants