-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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/xerrors: fails to compile on tip #32246
Comments
Changes in master was reverted in 3e2c522#diff-c93f2f0db26f58ae432e8d8f1dc9bd73 |
@agnivade |
Thanks. Replied. |
@agnivade |
Change https://golang.org/cl/177379 mentions this issue: |
@mpx Thanks comment. And yes, has been released go1.13beta1 but this version can't compiling I know that the discussion of the next error package implementation proposal takes a long time. also I know still discussing. also ping @rsc, @ianlancetaylor @bradfitz |
Is there any (hacky) workaround for now? Update: looks like this helped:
|
Just |
Change https://golang.org/cl/184937 mentions this issue: |
@zchee: thank you. Added:
to my |
* Set up CI with Azure Pipelines [skip ci] * Fix %PLATFORM% * Add Azure badge * Try to make nimble happy with windows PATH * rename steps [skip ci] * Mixed up posix/windows in pipeline * add missing ARCH: x86 to Linux32 * Linux "32bit" CI was actually 64-bit, remove it from now * Try to workaround path issues in windows * More crazy path workarounds + display gcc version (debug win 32-bit) * keep the bash workaround in * mingw path as separate task * Let's start a fresh day bout against Azure * fix powershell variable interpolation * make all scripts verbose to debug MacOS Go libp2p daemon script * Don't test on Azure macOS, xerrors issue due to Go version: - libp2p/go-libp2p-daemon#139 - status-im/nimbus-eth2#397 - golang/go#32246 * polish + reduce verbosity [skip ci]
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/CqTSV8-Wcg0
What did you expect to see?
Program compiles.
What did you see instead?
The text was updated successfully, but these errors were encountered: