-
Notifications
You must be signed in to change notification settings - Fork 18.5k
Open
Labels
GoCommandcmd/gocmd/goNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.modules
Milestone
Description
What version of Go are you using (go version)?
$ go version go version devel go1.19-dbbe4cca5d Tue Mar 8 21:35:38 2022 +0000 darwin/amd64
Does this issue reproduce with the latest release?
At least on tip.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env N/A
What did you do?
$ go mod init foo
go: creating new go.mod: module foo
$ go mod tidy
go: warning: "all" matched no packages
What did you expect to see?
An error message that doesn't mention all, since I didn't specify all anywhere. I understand why I do get this error message but it might be confusing in other cases.
I stumbled upon this when I accidentally ran go mod init twice where the second run explicitly asks me to:
go: to add module requirements and sums:
go mod tidy
What did you see instead?
go: warning: "all" matched no packages
jehiah
Metadata
Metadata
Assignees
Labels
GoCommandcmd/gocmd/goNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.modules