You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This promotes a connection hang during TLS handshake to a proper error.
This doesn't fully address #14539 because the error reported in that
case is a write-on-socket-not-connected error, which implies that an
earlier error during connection setup is not being checked, but it is
an improvement over the current behaviour.
Updates #14539.
Change-Id: I0571a752d32d5303db48149ab448226868b19495
Reviewed-on: https://go-review.googlesource.com/19990
Reviewed-by: Adam Langley <[email protected]>
go version
)?go version go1.6 darwin/amd64
go env
)?GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
Runnable example here: https://github.com/tamird/go-conn-repro
I expect that requests will either succeed or fail.
The test times out because a connection has hung in TLS handshake (both sides are trying to read). Stack trace:
This appears to be caused by errors not being propagated from the TLS handshake code.
The text was updated successfully, but these errors were encountered: