Note: I am building with GO111MODULE=on, from within my GOPATH.
I am building a command that imports a module defined as: module github.com/Figure53/figure53.com
Within that module, I import a package at github.com/Figure53/figure53.com/backend/remote, and it builds without issues.
I created a new file within a pre-existing package, and copy and pasted that import path. Somewhere along the way, I introduced a typo into the import path. The domain name in the import path was misspelled as gitdub.com.
I ran go build with GO111MODULE=on, and it hung silently until I cancelled it. I tried again a few times and got confused. It didn't seem to be CPU issue and I haven't experienced a feedback-less slow build for a while. After I stashed my changes, it built fine.
I read my diff, discovered my typo, fixed it, and the build worked again.
What did you expect to see?
I expected some indicator that go build was hung on trying to fetch a module, after shorter period of time. I also thought some sort of shorter timeout might make sense.
What did you see instead?
go build hung indefinitely.
Once I ran go build -v [...], I could see what it was working on, and the build hung indefinitely at:
It also is not a problem when the request returns quickly (as in an experiment I did to try to understand the problem where I changed the domain to one I control which will 404 quickly):
build github.com/Figure53/figure53.com/backend/act: cannot find module for path figure53.com/Figure53/figure53.com/backend/remote
I am loving this module system, by the way. It's gone very smoothly for the most part. Thanks for all the great work!
The text was updated successfully, but these errors were encountered:
gitdub.com is a parked domain, and appears to hang indefinitely for HTTPS requests. We probably can't fix the hang, because we can't distinguish between a slow server and an invalid one, but we can at least do something to clarify which operation is hung.
bcmills
changed the title
cmd/go: go build quietly hangs trying to download invalid module URL
cmd/go: describe stuck ops when terminated by signal
Jan 17, 2019
What version of Go are you using (
go version
)?go version go1.11 darwin/amd64
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOCACHE="/Users/ccahoon/Library/Caches/go-build"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
What did you do?
Note: I am building with
GO111MODULE=on
, from within my GOPATH.module github.com/Figure53/figure53.com
github.com/Figure53/figure53.com/backend/remote
, and it builds without issues.gitdub.com
.go build
withGO111MODULE=on
, and it hung silently until I cancelled it. I tried again a few times and got confused. It didn't seem to be CPU issue and I haven't experienced a feedback-less slow build for a while. After I stashed my changes, it built fine.What did you expect to see?
I expected some indicator that
go build
was hung on trying to fetch a module, after shorter period of time. I also thought some sort of shorter timeout might make sense.What did you see instead?
go build
hung indefinitely.Once I ran
go build -v [...]
, I could see what it was working on, and the build hung indefinitely at:Fetching https://gitdub.com/Figure53/figure53.com/backend/remote?go-get=1
It also is not a problem when the request returns quickly (as in an experiment I did to try to understand the problem where I changed the domain to one I control which will 404 quickly):
build github.com/Figure53/figure53.com/backend/act: cannot find module for path figure53.com/Figure53/figure53.com/backend/remote
I am loving this module system, by the way. It's gone very smoothly for the most part. Thanks for all the great work!
The text was updated successfully, but these errors were encountered: