Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go : Errors in `go get all` cause the tool to stop and not finish the work #34451
What version of Go are you using (
Ok, I see. I've been trying to figure out these differences.
When it is said, update "indirect" dependencies, does that mean my cache contains versions of a deps, deps that are potentially higher than listed in that deps own module file?
Though there is still a problem because since this versioning issue exists, it is causing
version selection works by building out a graph of dependencies recursively
"indirect" means not directly imported by your packages (dependency of a dependency, dependency under specific conditions (test, build tags))
cache just saves you a roundtrip to remote servers, which version is used is still decided by building out he graph of needed dependencies
I get that, thanks! Maybe I am having UI / useability issues?
I felt like something was now partially updated :( I am left wondering if I am in an odd state? Did the tooling rollback or was nothing even updated? It would be nice to be told that. I am clueless.
I would like a warning with a prompt (Y/N) from the tooling anytime you are about to update anything indirectly. There are so many switches and combinations, you could do this when you don't want to.
In fact, maybe a mode that prompts anytime the go.mod or go.sum file will be touched. That would give me the opportunity to pause and try to understand what I just did. Eventually I could turn that off.
This is the same underlying problem as #30831: prior to modules, the repository lacked an indication of its canonical import path. GOPATH mode did not verify import paths unless an
(It is important to detect this error because packages within a repo or module may
There are several possible short-term workarounds:
I notice that you already found and applied workaround (1).
Long term, we need better support for repositories whose import paths have changed. That is tracked in #30831.