Skip to content
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

fix: additional excessive go binary warnings #1432

Merged
merged 1 commit into from
Jan 3, 2023

Conversation

jedevc
Copy link
Contributor

@jedevc jedevc commented Jan 3, 2023

⬆️ Follow-up to #1424.
🐛 Fixes #1403.

The original fix b125ea8 didn't catch all the excessive warnings, it seems like getArches can also be called on binaries that aren't necessarily go binaries, so the messages from this should also be Trace instead of Warn

The original fix b125ea8 didn't catch
all the excessive warnings, it seems like getArches can also be called
on binaries that aren't neccessarily go binaries, so the messages from
this should also be Trace instead of Warn.

Signed-off-by: Justin Chadwell <me@jedevc.com>
@kzantow kzantow merged commit 8d36b21 into anchore:main Jan 3, 2023
GijsCalis pushed a commit to GijsCalis/syft that referenced this pull request Feb 19, 2024
The original fix 6560273 didn't catch
all the excessive warnings, it seems like getArches can also be called
on binaries that aren't neccessarily go binaries, so the messages from
this should also be Trace instead of Warn.

Signed-off-by: Justin Chadwell <me@jedevc.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Excessive "unable to read golang buildinfo error=not a Go executable file" warnings in versions after v0.62.1
2 participants