Conversation
This should fixes issues we are getting with `go.mod` files containing the `toolchain` directive. See google/go-licenses#128. Signed-off-by: Matthias Wessendorf <mwessend@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: matzew The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Tekton was doing similar before: I was getting a lot of hence I am proposing this |
|
@matzew what's the exact error related to |
|
I personally find this a bit annoying: Am I the only one w/ the |
| function check_licenses() { | ||
| # Check that we don't have any forbidden licenses. | ||
| go_run github.com/google/go-licenses@v1.6.0 \ | ||
| go_run github.com/google/go-licenses@v1.0.0 \ |
There was a problem hiding this comment.
We are going back? 🤔 Ok I see:
In v1.1, we made a breaking change of no longer supporting non go modules managed projects
Tekton has it (and go license have breaking changes) but is it a failure or warning? Does it happen on the CI too or is it local? 🤔
There was a problem hiding this comment.
There are warning in various CI logs, but I haven't found exit status 1.
There was a problem hiding this comment.
Do we really want to use some non-gomod deps?
/hold
There was a problem hiding this comment.
Do we really want to use some non-gomod deps?
Note the errors which indicate go-licenses is expecting Go standard library code to be Go Modules (Package crypto/aes does not have module info.), which seems to be a bug.
What's the command you are running it through here? |
|
I can confirm also experiencing issues here with sigstore/policy-controller. This PR was failing when an update added a toolchain directive. The errors coming from go-licenses show that it's expecting go stdlib packages to be go modules, for example: The check passed when the toolchain line was removed. I don't understand the root cause, but lots of people are pinning to go-licenses 1.0.0 according to google/go-licenses#128. |
This should fixes issues we are getting with
go.modfiles containing thetoolchaindirective.See google/go-licenses#128.