Custom Query (204 matches)

After fixing #19 I found out that our git is very slow when cloning over HTTPS with USE_CURL_MULTI defined. This define is automatically enabled for all recent versions of CURL and causes git to use several HTTP streams for talking to the server (which in theory should improve the overall performance).

While working on #19 I disabled USE_CURL_MULTI to simplify debugging HTTP transfers. However, now, when I enabled it back, I noticed that the clone speed significantly decreased. For instance, cloning ​https://github.com/psmedley/gcc with *no* USE_CURL_MULTI gives us around 200 KiB/s second. When USE_CURL_MULTI is enabled, the speed drops to 25 KiB/s (i.e. almost 10 times slower). This is not acceptable.

I'm not 100% sure if it's a git or curl problem. At least, when I try to use CURL.EXE to directly download a ZIP from github it is as fast as it should be (around 200 KiB/s) but I'm not sure if CURL.EXE uses multiple streams internally or not (and there are no command line options to control this).

Note that this applies to git 2.0.0 (built from the dmik branch ATM).

An attempt to use any command implemented as a shell script (e.g. git submodule or even git pull fails with the following message):

trace: exec: 'git-pull'
trace: run_command: 'git-pull'
fatal: cannot exec 'git-pull': Invalid executable file format

There are actually two things for git-pull in git-core: : git-pull.sh (which is a shell script) and git-pull.exe (which is a symlink to git-pull). I recall that these .exe symlinks are created so that LIBC exec could recognize the file as an executable and then find the right file by following the symlink and then start it with the right shell after finding out it's a shell script. But this logic seems to break at some stage. I need to check why. The git-pull command is pretty much critical and must work.

Note that this applies to git 2.0.0 (built from the dmik branch ATM).

Final testing shows that git pull is somehow broken in git 2.0.0 (dmik branch). An attempt to pull from any repo gives something like this:

D:>git pull -v
Password for 'https://dmik@bitbucket.org':
From https://bitbucket.org/dmik/test
 = [up to date]      master     -> origin/master
 - not something we can merge7293a3f24e44318563

The last line looks quite bogus. We can't release like that, it needs fixing.