-
Notifications
You must be signed in to change notification settings - Fork 86
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
err: encoding/hex: odd length hex string #80
Comments
Thanks for reporting this. I don't have a mac so a bit hard to test as this is likely mac specific. However, I wonder if you would be able to share a token (that is expired ofc. and doesn't have secret information) which causes this, because I assume it could be somehow related to the "password" input which trigger this. go-keyring/.github/workflows/go.yml Line 56 in 2a11960
|
v0.2.0 has an open bug: zalando/go-keyring#80 And this dependency has been upgraded and then downgraded twice now. I propose that we just ignore the dependency completely until there's a known fix.
Prevent dependabot from upgrading broken dep v0.2.0 has an open bug: zalando/go-keyring#80 And this dependency has been upgraded and then downgraded twice now. I propose that we just ignore the dependency completely until there's a known fix.
I believe this error is a byproduct of the truncation seen in #84 .
@mikkeloscar from what I can tell, most arbitrary string larger than 1996 bytes are candidates for the
As OP indicated above, downgrading to v0.1.1 fixes this issue. |
We now merged #86 which should improve the experience here. |
I noticed that in using the chanzuckerberg/aws-oidc project that there was a version upgrade to zalando/go-keyring v0.2.1.
It appears that in zalando/go-keyring v0.2.0, this change caused chanzuckerberg/aws-oidc to have this error.
Downgrading chanzuckerberg/aws-oidc back to zalando/go-keyring v0.1.1 fixed the problem but I don't think I understand context enough to why the accidentally breaking change was introduced in zalando/go-keyring v0.2.0
The text was updated successfully, but these errors were encountered: