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

Jump to bottom

cmd/go: "go env" becomes unusable after I run "go env -w" wrongly. #34880

Closed
dotaheor opened this issue Oct 13, 2019 · 3 comments
Closed

cmd/go: "go env" becomes unusable after I run "go env -w" wrongly. #34880

dotaheor opened this issue Oct 13, 2019 · 3 comments
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.14

Comments

@dotaheor
Copy link

What version of Go are you using (go version)?

$ go version
go version go1.13.1 linux/amd64

Does this issue reproduce with the latest release?

true

What did you do?

$ go env -w GO111MODULE==on
$ go env
go: unknown environment setting GO111MODULE==on
$ go env -w GO111MODULE=on
go: unknown environment setting GO111MODULE==on
$ go env -w GO111MODULE=
go: unknown environment setting GO111MODULE==on
@mvdan
Copy link
Member

mvdan commented Oct 13, 2019

This seems to me like a variation of #34194; that involved an invalid GOOS/GOARCH pair, while this seems to involve an unknown variable name.

/cc @bcmills @jayconrod

@mvdan mvdan added the NeedsFix The path to resolution is known, but the work has not been done. label Oct 13, 2019
@mvdan mvdan added this to the Backlog milestone Oct 13, 2019
@mvdan mvdan self-assigned this Oct 13, 2019
@mvdan mvdan modified the milestones: Backlog, Go1.14 Oct 13, 2019
@mvdan
Copy link
Member

mvdan commented Oct 13, 2019

On second thought, this involves an invalid GO111MODULE value. Sent a CL.

@gopherbot
Copy link

Change https://golang.org/cl/200867 mentions this issue: cmd/go: refuse -w with an invalid GO111MODULE

@ALTree ALTree mentioned this issue Nov 4, 2019
Closed
@ALTree ALTree mentioned this issue Nov 13, 2019
Closed
@oiooj oiooj mentioned this issue Nov 13, 2019
Closed
@ALTree ALTree mentioned this issue Jan 16, 2020
Closed
@golang golang locked and limited conversation to collaborators Oct 13, 2020
@rsc rsc unassigned mvdan Jun 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Go1.14
Development

No branches or pull requests
3 participants
@mvdan @gopherbot @dotaheor