-
Notifications
You must be signed in to change notification settings - Fork 638
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
Git: run detached #1314
base: master
Are you sure you want to change the base?
Git: run detached #1314
Conversation
Ahah nice I often have this error ;) |
I am not sure if I have looked at vscode (they also use git via spawn) and they use |
I only added the |
Hmm, I understand the issue but I don't think I don't think that is a good idea as there maybe just hung threads running without user's awareness, especially even after ungit process is dead. There was a PR or code changes I've done long time ago around doing timeouts on git processes but I think I've lost it by now. I think something similar might be a better solution |
Ok, so if it runs detached there's a chance it hangs for some reason other than waiting for a password and then it won't get killed? Doesn't the timeout work for that? (Didn't check) |
Yes it can cause orphaned threads. I could depends on the implementations. |
This prevents git hanging for asking ssh passphrases
In the docs it says:
So I think running detached is safe. Closing stdin is not enough, it will still prompt me for keys when I run |
This prevents git hanging for asking ssh passphrases, like when you run it inside vscode with an empty ssh-agent.
Now when I run
SSH_AUTH_SOCK= npm start
, it immediately errors in the web UI instead of hanging.