You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
maybe this issue can be closed, i still wanted to open it to keep it as reference.
summary
i never had problems with git, putty and plink but after upgrading from git 2.14.1 to git 2.19.0 my remote commands (i tried pull and push) took ages (~30sec for a pull of a not modified repo).
problem started after upgrading git 2.14.1 to git 2.19.0
only having the problem pull/push to gitlab.com
no problem pull/push to github.com
also had the problem while only calling plink -v -T git@gitlab.com
friend of mine could reproduce the problem (no problem with plink before installing git, slow connection after installing it, deinstalling and reinstalling solved his problem. he was not able to reproduce the problem again)
the issue on gitlab has 2 upvotes, so it looks like i am not alone
workaround was to tunnel the connection over a linux server
currently it works again, cannot relate a specific action to it
[x ] I was not able to find an open or closed issue matching what I'm seeing
maybe this issue can be closed, i still wanted to open it to keep it as reference.
summary
i never had problems with git, putty and plink but after upgrading from git 2.14.1 to git 2.19.0 my remote commands (i tried
pull
andpush
) took ages (~30sec for a pull of a not modified repo).my tests resulted in:
plink -v -T git@gitlab.com
Setup
defaults?
Any other interesting things about your environment that might be related
to the issue you're seeing?
cannot use ssh-agent (connection timeout). i assume because of my firewall
no problems with git before updating to git-2.19.0. i assume i had 2.1.14.1before (because its still in my download folder)
Details
Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
cmder, bash & cmd (tried all three)
What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
fast response
very slow executing (28sec) even if the repo is small and no changes to pull. having
GIT_TRACE=1
set i could narrow it to the execution ofplink
URL to that repository to help us with testing?
had the problem with gitlab.com repositories
test repos:
The text was updated successfully, but these errors were encountered: