-
Notifications
You must be signed in to change notification settings - Fork 1k
dep hangs when subcommands try to read from stdin #1476
Comments
So seeing this, I did some investigation as to why it just froze like this. The freeze occurs in
I tried running the
So I assumed that the freeze up occurs because On my own run of |
Possible SolutionIn trying to find a solution for this I stumbled across the "GIT_SSH_COMMAND" environment variable. Just like the "GIT_ASKPASS=", "GIT_TERMINAL_PROMPT=0" variables are set, if the |
hmm, interesting. I don't think we can do that safely, though, as we do need to support the case - at least eventually, we clearly don't now - where passworded login works. see Masterminds/glide#411, which is that, but also a step further. |
I think I am also able to reproduce this issue. My |
is it possible to sniff the state of running subprocesses to see if they're blocked reading from stdin? we might be able to use that to make a smart decision here. |
I hit this with my encrypted Right now it just silently fails. If, as above, |
By the way setting env variables in the current codebase to disable prompting doesn't work as expected. Line 265 in b2afe44
If And the reason of the hang is that |
Just for anyone who encounters this the current workaround is to use
More unfortunate is that |
/cc |
What version of
dep
are you using (dep version
)?v0.3.2-163-g5d5088d6
What
dep
command did you run?I ran
dep init -gopath -v
while in a directory only containing the file main.go below.My intention was to add a repo from my own gopath under src/github.com/test/color (for testing purposes). I deleted the .git information in this directory.
What did you expect to see?
I expected this to work: because of the -gopath flag it would just go and get the repo info from the gopath.
If for some reason it didn't do this and tried to get the information from github, I would have expected it to fail.
What did you see instead?
This text came up. I waited a long time for it to do something (10-20 mins) and it was just stuck here.
The text was updated successfully, but these errors were encountered: