New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/crypto/ssh: Wrap error in NewClientConn #45207
Comments
cc @FiloSottile |
I see that simply changing the |
I'm not sure why changing |
@nvx Yes, backwards compatibility is no longer an issue, so then this would be a 1 line change. |
Change https://go.dev/cl/448595 mentions this issue: |
I have some code that wants to check if a |
Fixes upsteam bug golang/go#45207, which already has a open PR that's been blocked for months.
Fixes upsteam bug golang/go#45207, which already has a open PR that's been blocked for months.
Fixes upsteam bug golang/go#45207, which already has a open PR that's been blocked for months.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
https://play.golang.org/p/CdUXyBdUq2g
What did you expect to see?
Using type assertion or
errors.As
for things like*net.OpError
on errors returned byNewClientConn
works.What did you see instead?
The returned error is a
*errors.errorString
due to the fact that it's returned usingfmt.Errorf
and%v
instead of%w
.The text was updated successfully, but these errors were encountered: