无法使用Windows命令在Windows 2008服务器中克隆GitLab存储库

Question

I need to be able to clone GitLab repositories in a 64-bit Windows 7 laptop and in a 32-bit Windows 2008 Server using Windows command line – it must be through Windows command line. I installed Git for Windows in both, using pretty much the same options. Running the git clone command below works in the laptop BUT it does not in the server:

H:>git clone --branch master http://username@gitlab.company.com/username/test.git e:\\gitlab\\test Cloning into 'e:\\gitlab\\test'... fatal: full write to remote helper failed: Broken pipe
H:>error: remote-curl: error reading command stream from git

I searched the above error messages and I found that the common suggestions are to check Network connection to the repositories and the AntiVirus. I did both with the help of a Windows System Administrator and we got nowhere so I started looking at the git config options and I while running the following commands:

H:>git --version git version 2.21.0.windows.1
H:>git config --global --edit
H:>git config --global --get gui.maxfilesdisplayed
20000
H:>set GIT_TRACE=1
H:>git config --global --list 08:45:23.918834 exec-cmd.c:236 trace: resolved executable dir: C:/Program Files/Git/mingw32/bin 08:45:24.106035 git.c:419 trace: built-in: git config --global --list 08:45:24.277636 run-command.c:643 trace: run_command: unset GIT_PAGER_IN_USE; LESS=FRX LV=-c less Missing filename ("less --help" for help)
H:>

I found out that I can 1 - edit the global and system configuration files 2 – list a specific option BUT I cannot list their options using –list or --list --show-origin.

I wonder is the issue with the config is impacting the git clone command. Any suggestions?

Thanks,

Answer 1

After 7 months trying to figure this out, I found the exact same issue reported by Demon-Ru here: https://github.com/git-for-windows/git/issues/1742#issuecomment-473515386

I followed the suggestion by DeeDeeG and installed Git for Windows 2.16.1.windows.1 - https://github.com/git-for-windows/git/releases/tag/v2.16.1.windows.1 on the server and both issues were resolved.

Thanks everyone how look at helping! Be good