git fatal problems (12)

reference: https://stackoverflow.com/questions/28570836/git-cloning-remote-end-hung-up-unexpectedly-tried-changing-postbuffer-but-stil

problem info:

# git clone https://github.com/snivel/misc.git
Cloning into 'misc'...
remote: Enumerating objects: 49, done.
error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: unpack-objects failed

How to solve:

The GIT_HTTP_MAX_REQUEST_BUFFER environment variable (or the http.maxRequestBuffer config variable)

may be set to change the largest ref negotiation request that git will handle during a fetch; any fetch requiring a larger buffer will not succeed.

This value should not normally need to be changed, but may be helpful if you are fetching from a repository with an extremely large number of refs.

The value can be specified with a unit (e.g., 100M for 100 megabytes). The default is 10 megabytes.

or :

reference:https://stackoverflow.com/questions/38378914/git-error-rpc-failed-curl-56-gnutls

git config --global http.postBuffer 1048576000

how to debug:

set the output to be more verbose, and somehow it worked. 

export GIT_TRACE_PACKET=1; export GIT_TRACE=1; export GIT_CURL_VERBOSE=1

 

猜你喜欢

转载自www.cnblogs.com/lianghong881018/p/12094975.html