-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
cmd/go: get does not respect GOFLAGS="-mod=readonly" #32147
Comments
It would be nice if the semantics and intended use of that line in the |
That's #30791. |
I'm not able to reproduce the observed behavior using the repro steps provided.
|
I am now unable to repeat this locally for reasons I have no clue about. So I have investigated further on travis and see that the mutation occurs prior to invoking |
@kortschak, that Travis log unfortunately doesn't tell us much. It seems likely that the culprit is an If you believe that the error is in |
OK, I can see where this is coming from now. The travis This issue does raise another problem though. I have worked around the failure by adding a go directive line to the go.mod ( |
I have debugged this on travis and now have a local reproducer. The problem was not with
|
This looks like it's related to #30345. |
See #26850 (comment). |
Duplicate of #26850 |
Given that this breaks builds in a way that has not been accounted for and has can only be worked around using a technique that has not been documented to behave in a way that will necessarily result in a sensible desired behaviour (and that you've suggested should break reasonable module configurations) would you please explain how to approach this if it is not going to be fixed. I've dealt with occasional frustrations with the approaches taken by the core team in feature roll out and planning in the past, but nothing that comes close to how modules is being handled. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
No - it cannot.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run
go test ./...
withGOFLAGS="-mod=readonly"
in gonum.org/v1/gonum. Originally noticed in a travis log.What did you expect to see?
No modification of go.mod
What did you see instead?
The text was updated successfully, but these errors were encountered: