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
Recently, I fixed a potential issue with the etcd client. During our review and discussion, we noticed that there are similar scenarios in the Go standard library. I conducted some tests and got the same results: https://go.dev/play/p/-1W0mi3EMQS
My perspective on this is here. If this is confirmed to be a bug, it might be necessary to perform a comprehensive review of similar usages in the standard library.
The commit which introduced "shouldRetryDial" feels like a hotfix to me: It sloppily tries to rediscover cancelation sources instead of tracking connection state.
Go version
go version go1.23.3 linux/amd64
Output of
go env
in your module/workspace:What did you do?
Recently, I fixed a potential issue with the etcd client. During our review and discussion, we noticed that there are similar scenarios in the Go standard library. I conducted some tests and got the same results: https://go.dev/play/p/-1W0mi3EMQS
My perspective on this is here. If this is confirmed to be a bug, it might be necessary to perform a comprehensive review of similar usages in the standard library.
What did you see happen?
What did you expect to see?
Never panicking
The text was updated successfully, but these errors were encountered: