Join GitHub today
crypto/tls: a timeout error on tls.Conn.Write is confusing #8071
SetWriteDeadline of tls.Conn describes "A zero value for t means Write will not time out. After a Write has timed out, the TLS state is corrupt and all future writes will return the same error." but the returned value on timeout is marked Temporary and it may be confusing. A suggestion: https://groups.google.com/d/msg/golang-nuts/UChb8wv6gvA/9R_g4ScTMiYJ
Hm, I have never imagined it's confusing.
My understanding from the discussion at golang-nuts is that the returned error value from tls.Conn should not be marked/colored "Temporary" when the underlying facilities are unable to provide communication functionality anymore.
In other words, a returned error value should represent the error, the definition is slightly different between SDOs, let's say it's "an incorrect internal state" here, precisely as much as possible for fault localization.