DEV Community

ChungWei Wei
ChungWei Wei

Posted on • Originally published at kmp.tw on

[Git] Git Push Get Hung Up Error

Situation

When Run git push , The Log Show fatal: the remote end hung up unexpectedly

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 10 threads
Compressing objects: 100% (3/3), done.
send-pack: unexpected disconnect while reading sideband packet
Writing objects: 100% (3/3), 9.94 MiB | 8.26 MiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
fatal: the remote end hung up unexpectedly
Everything up-to-date
Enter fullscreen mode Exit fullscreen mode

How To

Add Git Config And Re-Push Again

git config --local http.postBuffer 524288000

Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 10 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 9.94 MiB | 14.31 MiB/s, done.
Total 3 (delta 1), reused 0 (delta 0), pack-reused 0
remote: Validating objects: 100%
To https://git-codecommit.us-east-1.amazonaws.com/v1/repos/<your-repo>
   9115319..94a8c94  main -> main
Enter fullscreen mode Exit fullscreen mode

Root Cause

The Git http.postBuffer Default Is 1 MiB, So Need Change Config

http.postBuffer
Maximum size in bytes of the buffer used by smart HTTP transports when POSTing data to the remote system. For requests larger than this buffer size, HTTP/1.1 and Transfer-Encoding: chunked is used to avoid creating a massive pack file locally. Default is 1 MiB, which is sufficient for most requests.

Note that raising this limit is only effective for disabling chunked transfer encoding and therefore should be used only where the remote server or a proxy only supports HTTP/1.0 or is noncompliant with the HTTP standard. Raising this is not, in general, an effective solution for most push problems, but can increase memory consumption significantly since the entire buffer is allocated even for small pushes.
Enter fullscreen mode Exit fullscreen mode

Top comments (0)