-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: go get hangs #16104
Comments
Can you run |
No
Yes
But this should be transparent to |
I don't know why it works some times and not others, it's probably related to whatever is on disk at the time. If you remove the |
If I had to guess, because you've redirected https to ssh, something is hanging with the usual ssh prompt to accept an ssh fingerprint. Just a guess. |
I can wipe out the
Yes
Not the case.
(and just for clarification, this happens with all repos, not just this one) |
Can you please try again with the On Sun, Jun 19, 2016 at 3:34 PM, Patrick Hemmer [email protected]
|
Just sits there after that last line. |
Maybe this is a git bug, if git doesn't return then there is nothing the go On Sun, 19 Jun 2016, 15:38 Patrick Hemmer [email protected] wrote:
|
But it does return. As mentioned earlier,
Though that last line did lead me down another route of investigation. Killing the ssh control process (PID 23991) does make |
The I don't know why |
ssh isn't hanging, this is how it behaves when using the |
Is there some way that In general |
Unless However you could probably set the environment variable |
Also see #13453. |
Ahha! this can probably be closed as a duplicate then. |
It does look like the same underlying issue, so closing as dup.
|
CL https://golang.org/cl/31353 mentions this issue. |
Fixes #13453. Fixes #16104. Change-Id: I4e94f606df786af8143f8649c9afde570f346301 Reviewed-on: https://go-review.googlesource.com/31353 Reviewed-by: Quentin Smith <[email protected]>
go version
)?go env
)?success
hanging indefinitely
Additional info:
This has been happening to me for years (obviously on older versions of go), but it's mostly just an annoyance as I can usually just retry the
go get
once or twice and it'll succeed. Meaning this doesn't happen every time.When I send a
SIGQUIT
to the process, this is the output:I also have an
strace
available.The text was updated successfully, but these errors were encountered: