Skip to content
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 installation maybe interfering with plink & gitlab #1870

Closed
c33s opened this issue Oct 8, 2018 · 1 comment
Closed

Git installation maybe interfering with plink & gitlab #1870

c33s opened this issue Oct 8, 2018 · 1 comment

Comments

@c33s
Copy link

c33s commented Oct 8, 2018

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).

my tests resulted in:

  • detailed tests: https://gitlab.com/gitlab-com/support-forum/issues/3975
  • 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

Setup

  • Which version of Git for Windows are you using? Is it 32-bit or 64-bit?
$ git --version --build-options

git version 2.19.1.windows.1
cpu: x86_64
built from commit: 11a3092e18f2201acd53e45aaa006f1601b6c02a
sizeof-long: 4
sizeof-size_t: 8
  • Which version of Windows are you running? Vista, 7, 8, 10? Is it 32-bit or 64-bit?
$ cmd.exe /c ver

Microsoft Windows [Version 6.1.7601]
  • What options did you set as part of the installation? Or did you choose the
    defaults?
# One of the following:
> type "C:\Program Files\Git\etc\install-options.txt"
> type "C:\Program Files (x86)\Git\etc\install-options.txt"
> type "%USERPROFILE%\AppData\Local\Programs\Git\etc\install-options.txt"
$ cat /etc/install-options.txt

Editor Option: Notepad++
Custom Editor Path:
Path Option: CmdTools
Plink Path: C:\Program Files\Putty\plink.exe
SSH Option: Plink
CURL Option: OpenSSL
CRLF Option: LFOnly
Bash Terminal Option: ConHost
Performance Tweaks FSCache: Enabled
Use Credential Manager: Disabled
Enable Symlinks: Disabled
Enable Builtin Rebase: Disabled
Enable Builtin Stash: Disabled
  • 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.

git clone git@gitlab.com:c33s/git_speed_test.git
cd git_speed_test
git pull
plink -v -T git@gitlab.com
  • What did you expect to occur after running these commands?

fast response

  • What actually happened instead?

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 of plink

time git pull
Enumerating objects: 54, done.
Counting objects: 100% (54/54), done.
Delta compression using up to 12 threads
Compressing objects: 100% (49/49), done.
Writing objects: 100% (54/54), 34.21 KiB | 2.01 MiB/s, done.
Total 54 (delta 2), reused 0 (delta 0)
To gitlab.com:c33s/git_speed_test.git
 * [new branch]      master -> master

real    0m28.684s
user    0m0.000s
sys     0m0.062s
  • If the problem was occurring with a specific repository, can you provide the
    URL to that repository to help us with testing?

had the problem with gitlab.com repositories

test repos:

@c33s
Copy link
Author

c33s commented Oct 9, 2018

looks like it works now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant