-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Feature request: silently stops ssh-agent.exe when upgrading #4172
Comments
That's a great idea, and you can even contribute that change yourself:
|
Thanks for pointing me in the right direction |
@jeanmichel-nwsb If you do create a PR for this, it would probably be worth including |
Oups, I haven't used Pascal since I left engineering school in 1989... 🙄 I have identified part of the problem : the test in the line pointed by @dscho doesn't work because So I tried the following, backward compatible code: ProcessName:=Processes[Have].Name;
Position:=Pos('.exe',LowerCase(ProcessName));
if (Position>0) then SetLength(ProcessName,Position-1);
if ('ssh-add'=ProcessName) or ('ssh-agent'=ProcessName) or ('ssh-pageant'=ProcessName) or ('gpg-agent'=ProcessName) or ('scdaemon'=ProcessName) then
Processes[Have].ToTerminate:=True; It seems more or less to do the job but not before the page that list the processes to kill have appeared once |
This fixes git-for-windows/git#4172 Signed-off-by: Jean-Michel Mercier <jeanmichel.mercier@newsbridge.io> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Fixed with git-for-windows/build-extra#453 |
/add release note bug The installer is expected to stop GPG agents automatically, but there was a bug that prevented that from working, which has been fixed. The workflow run was started |
Setup
defaults?
to the issue you're seeing?
Details
git-bash (but that's not relevant to the request)
Minimal, Complete, and Verifiable example
this will help us understand the issue.
Running setup for upgrading an existing git-for-windows while ssh-agent is already running in the background.
Seamless upgrade with no or little user interaction.
The installer comes up with an error message telling that ssh-agent.exe is running in the background.
User have to open the task manager, go to the "Details" tab, find ssh-agent.exe and kill it in order to continue the upgrade process.
This is a bit tedious and unfriendly
I am suggesting that the installer either silently kill the running ssh-agent.exe, or at least offers to do it on behalf of the user when popping up the message.
As far as I remember, this behavior has been consistent since I am using Git-for-Windows for the last 3 years.
Thanks
Beside that, I LOVE git-for-windows and git-bash. I prefer using that than WSL2.
Thanks for the job.
URL to that repository to help us with testing?
not applicable
The text was updated successfully, but these errors were encountered: