net: Checking errors for EPIPE and ECONNRESET requires syscall #8319
Comments
I don't know what to do about this. We could use io.ErrUnexpectedEOF for Read, and maybe for Write too. Unclear. I'm not thrilled about hacks in net because writing to pipes has the same problem. But I'm not thrilled about hacks in os either. Leaving for 1.5. Labels changed: added release-go1.5, removed release-go1.4. |
"readfull EOF:*net.OpError read tcp 172.19.13.222:51753->172.19.5.50:9091: wsarecv: An established connection was aborted by the software in your host machine. |
This could be resolved using the go1.13 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: