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: look only at dependencies in use in 'go run' #31057
Comments
Does go build with this case have the same problem? I've been seeing surprising output from go build lately. |
I’m not sure. I still haven’t fully wrapped my head around modules, but I have noticed that cmd/go needs a surprising amount of network access. (I’m used to basically everything working without the internet, and am disconcerted by the notion that I do not understand enough to be able to plan for an airplane trip, much less not have to plan at all.) But I am working under the assumption that all of the foregoing is my problem. |
It might not be just your problem. I see much network access (and slowness) that I cannot explain. |
Could you attach the output of If you're using I've been testing these sorts of issues using For the command line you provided, a
|
CC @jayconrod |
Ahhh. I was indeed using Thanks for the heads up about how to narrow down and reproduce these. |
With no network access:
But the imports used by
mkbuiltin.go
are 100% standard library with no dependency that I see on those three repos.It looks to my untrained eye like the
cmd/compile/internal/gc
package depends on those repos, but notmkbuiltin.go
. Assuming that that is accurate, and given thatgo run x.go
is effectively independent of the location ofx.go
on disk, it seems to me that mygo run
command should have succeeded.cc @bcmills @jayconrod
Apologies if this is a duplicate; I'm having a hard time keeping track of the various go modules issues.
The text was updated successfully, but these errors were encountered: