-
Notifications
You must be signed in to change notification settings - Fork 100
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
color.SetOutput() panics on go 1.17 #46
Comments
tsachiherman
pushed a commit
to algorand/go-algorand
that referenced
this issue
Oct 28, 2021
Summary @barnjamin mentioned in #2899 that labstack/gommon/issues/46 has a similar issue. Should be fixed by up version of sys. Closing #2899.
cce
pushed a commit
to cce/go-algorand
that referenced
this issue
Oct 28, 2021
Summary @barnjamin mentioned in algorand#2899 that labstack/gommon/issues/46 has a similar issue. Should be fixed by up version of sys. Closing algorand#2899.
sparshev
added a commit
to adobe/aquarium-fish
that referenced
this issue
May 12, 2022
Now fish supports the naming that includes strict image version. And by the way: * Updated the echo dep due to panic in go 1.17: labstack/gommon#46 * Fixed start of the not allocated resources during node init * Updated the test scripts and created script to fill images
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem is on this line:
gommon/color/color.go
Line 146 in 4919956
The panic is fixed v0.0.14 of the upstream
go-isatty
, via mattn/go-isatty#66Root cause is here:
golang/go#47776
Here's what the panic looks like on go 1.17:
The text was updated successfully, but these errors were encountered: