Open lysShub opened 4 months ago
system test passed on windows and linux
Can you help describe the problem in more detail? Is this contradicted in a doc somewhere, or does this differ from other implementers of net.Conn
?
Can you help describe the problem in more detail? Is this contradicted in a doc somewhere, or does this differ from other implementers of
net.Conn
?
In most operating systems, writing to a closed TCP connection will return an error, including conn.Write([]byte{})
,but gonet will return 0 and nil
We'd definitely accept a PR with this change!
Description
Steps to reproduce
No response
runsc version
No response
docker version (if using docker)
No response
uname
No response
kubectl (if using Kubernetes)
No response
repo state (if built from source)
No response
runsc debug logs (if available)
No response