Best IT Recipes

Hanging on "POST git -receive-pack (chunked)"

I will be honest, I know very little about the internal functions of git.

I set and fixed the 40 MB directory, but when I came to click ...

$ git push --verbose --progress Pushing to https://acron0@bitbucket.org/acron0/project.git Password for 'https://acron0@bitbucket.org': POST git-receive-pack (chunked)

It was like this for 20 minutes. I guess it hangs, but ... is there anything I can do to find out why?

+50
git version-control
May 28 '12 at 20:44
source share
5 answers

This is a bug in Git; when using HTTPS, it will use encoded encoding for downloads above a certain size. This does not work.

A trivial fix is ​​to tell git so that it doesn't crash to some ridiculously large size value, for example:

 git config http.postBuffer 524288000
+82
Jan 30 '13 at 0:10
source share

Maybe your credentials. Use the git + ssh protocol instead of https.

+19
May 28 '12 at
source share

Using SourceTree to click on BitBucket I get this error every few months. Turns out I just have to wait another five minutes, and that in itself. He seems to have hanged himself, and the temptation is simply to undo and retry, but perhaps hang there a little longer. I know that they have already answered this, but my commits were probably a couple of hundred kb, not 40mb, which the original poster says.

+7
Feb 13 '15 at 9:08
source share

If you found this site due to a BitBucket crash with this error message, check the answers to this question:

  • how to use git extension with bitbucket repository?

In particular, a comment by Nicola Pickering and Simon Tuzey about which part of the key should be inserted into the BitBucket dialog.

+1
Nov 24 '13 at 15:35
source share

With Git 2.13 (Q2 2017) you can install http.postBuffer on a really large number (i.e. more than ulong on some platforms).

See commit 37ee680 (April 11, 2017) by David Turner ( csusbdt ) .
(merger of Junio ​​C Hamano - gitster - in commit 4c01f67 , April 24, 2017

http.postBuffer : allow the full range of ssize_t values

Unfortunately, in order to push some large repositories where the server does not support striping, sometimes http postbuffer exceeds two gigabytes.
On a 64-bit system, this is normal: we just malloc a larger buffer.

This means that we need to use CURLOPT_POSTFIELDSIZE_LARGE to set the buffer size.

0
Apr 24 '17 at 21:22
source share


More articles:


All Articles