cmd/go: go get of nested module picks version from outer module #56974
What is the URL of the page with the issue?
What did you do?
I have a repo, github.com/twmb/franz-go with a module at the top-level repo root and other modules at subdirectories. Whenever I release the repo root (push a tag), I can
I've managed tags like this for over a year now, and the wait for submodules has never been this long.
What did you expect to see?
What did you see instead?
for 30 minutes
The text was updated successfully, but these errors were encountered:
Yes, the nested module was pushed immediately before. The screenshot above is a small indication of the timing -- I pushed firstname.lastname@example.org, waited about 30s, and then in then in franz-go/pkg/kadm,
I just tried again and was still unable to
Screenshot attached showing this was still problematic after 9 hours:
Since things are now "fixed" locally, I don't know what extra debugging I'll be able to do (until the next release...). Let me know if there's anything more I can look into / provide that can help.
Update: actually I was able to do one more bit of investigating. The same thing was happening on my other laptop. I was able to resolve this locally by running:
My completely uninformed guess is that if
(other laptop is Linux [Ubuntu] but has similar defaults)
If this happens again, you could check that by adding the
Barring that, I don't think we have enough information to investigate further.
This is happening on v1.20.5.
I released a new module, email@example.com.
The Go command does not issue any http requests. I suspect it's because I have old franz-go versions in my mod cache:
So go sees firstname.lastname@example.org exists, but because kmsg is a separate module, the pkg is not in that top-level module: