Pushing commits to origin with larger projects resulting in "SSL error: syscall failure: Broken pipe"

[ksdhans]

As my project grows, I'm starting to get "sgit push origin master" failing with the error: "libgit2 error (2): SSL error: syscall failure: Broken pipe"

So far I've been able to work around the issue by doing an sgit clone to a new directory, copying the changes, and committing from the new directory. That's a real pain, though.

GitLab says that there are 87.3 MB of files, and the entire directory on my Amiga is round 381MB. The last commit that failed was less than 30KB large, so it's NOT the size of the commit that's causing the failure.

The freshly cloned directory is about 275MB, and its .git directory is about 1MB smaller. The rest of the difference is the build directory, which is excluded from the repository.

One other observation: after entering the username and password, CPU usage goes to 100% for over a minute, followed by a minute of idle, and then the "broken pipe" error is displayed. It's possible that the "broken pipe" is just a side-effect of another failure (whatever is causing the 100% CPU usage for so long).

[ksdhans]

Just encountered this again. I usually avoid it by pushing every individual commit to "origin," but this time I have a somewhat larger update.

Being unable to push your commits to the server is a serious problem. It basically stops you dead in your tracks. There's no point in continuing work, because you can't push any of it to the master repository.

[foman]

It seems a libgit2 issue