-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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: modules with empty go.mod files not diagnosed well #25272
Comments
We are seeing something that seems very likely to be related since it is a nested package in dcrd. However, rather than not being able to find the module, instead the dependency solver believes the nested module is provided by the parent module despite the parent module not including it as evidenced by looking in This can currently be reproduced as of dcrd commit be318f5a by navigate to the The following are the results:
We can verify the
For some extra data, here are the relevant tags:
|
@dcrd I think your problem is more like #26250. Fix CL going out today. @IngCr3at1on, the first problem is that the go.mod files checked into the repo are empty. They need to have a module line, like
and
I will make this issue track having a good diagnosis of this condition. Once those go.mod files are updated (and new tags added), then I think you'll be up against #26250. Watch for that issue to be closed. |
comment deleted (possibly separate issue, seems resolved). |
Issue seems incidentally solved by #45713 which added a more explicit message when go.mod is empty.
|
I can't actually decide if this is a bug or just me doing something wrong....
What version of Go are you using (
go version
)?go version go1.10.1 linux/amd64
go version go1.10.1 linux/amd64 vgo:2018-02-20.1
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
in a working directly create a main:
and a go.mod
touch go.mod
Or simply pull down
github.com/IngCr3at1on/bugexample
What did you expect to see?
The program should compile
What did you see instead?
Initially only the tag
v0.1.0
existed; someone in the #vgo channel on Gopher's Slack suggested I add the tagx5424/v0.1.0
but that doesn't seem to make a difference.It's worth adding that the issue reminds me of #24605 but I'm not sure if they're the same...
The text was updated successfully, but these errors were encountered: