-
Notifications
You must be signed in to change notification settings - Fork 388
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
Regression in v0.11.1
: Fails with could not parse Go build info
#666
Comments
Thanks for reporting this! It looks like the problematic importpath is
(the other image in that YAML builds fine). Building that binary locally and running
And that's the line causing us trouble -- that's What's even weirder, when I build that package with
But it can be parsed with
(note the suspicious newline after the I wonder if there's some subtle and annoying incompatibility between the output of In the meantime, upgrading to 1.18 or Thanks again for reporting! 👍 |
Thx for the quick reply! I pinned the |
Not sure if this is the same issue or a different one, but with
What is the go command that is being parsed so I can figure out what the deal is? Adding |
SBOMs are generated by running |
In all these cases it would be relevant to say how you installed If you install the prebuilt binary for |
go version -m output
|
Yeah, if I had to guess, I'd say the newline after each
I can't imagine that was an intentional choice by the Go team. |
Is there also a problem with I use ASDF to locally switch different versions of Go since we have some apps using Google AppEngine on its latest Go 1.16 (I know, ugh), and Kubernetes apps on shiny new Go 1.18. |
Also, I'm on darwin amd64, but encountered the problem in github actions for Linux. |
Maybe? But it sounds like that's not the main issue here. It sounds like Go-1.18-compatible code might be incapable of parsing Go-1.17-produced output, and maybe vice versa. What a headache. |
@jdolitsky and I took a look at this, and it appears to be an upstream go v1.18 bug with the new |
I saw couple of issues referencing a similar error, but this should have been resolved in
v0.11.x
. However, we just noticed in our pipelines, that withv0.11.1
the following error is thrown (again):error during command execution:error processing import paths in "-": error resolving image references: parsing build info: could not parse Go build info: line 5: expected 3 columns for replacement; got 2
Reverting the pipeline back to
v0.11.0
fixes it.Go version:
v1.17.7
Example workflow run where this is observed with
v0.11.1
: https://github.com/vmware-tanzu/sources-for-knative/runs/5621359754?check_suite_focus=trueWorking run reverting back to
v0.11.0
:https://github.com/vmware-tanzu/sources-for-knative/runs/5626066023?check_suite_focus=true
The text was updated successfully, but these errors were encountered: