Git Push Fails with RPC failed; curl 55 SSL_write() 返回 SYSCALL，errno = 10053
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/46790394/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Git Push Fails with RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053
提问by Nonlin
Full list of info
完整的信息列表
Counting objects: 1945, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (1935/1935), done.
rror: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 10053
atal: The remote end hung up unexpectedly
Writing objects: 100% (1945/1945), 3.15 GiB | 1.21 MiB/s, done.
Total 1945 (delta 231), reused 0 (delta 0)
fatal: The remote end hung up unexpectedly
Everything up-to-date
As far as I can tell, there is no file larger than 150MB, using the latest Git version. I've been able to push with no issue up until I added lots of new assets to my project (around 3GB worth) and now I get this.
据我所知，使用最新的 Git 版本，没有大于 150MB 的文件。我一直能够毫无问题地推进，直到我向我的项目添加了许多新资产（价值约 3GB），现在我明白了。
What I have tried is increasing the postBufferfor both httpand httpsto 2097152000
我曾尝试是增加了postBuffer两个http，并https以2097152000
I should also note that I did originally have a large zip file that was not ignored (400MB) but I deleted it and made a new commit, however, this may not have been the proper way to have gotten rid of this, as I guess it will still try to push it out since the commit before the latest had it?
我还应该注意，我最初确实有一个未被忽略的大 zip 文件（400MB），但我删除了它并进行了新的提交，但是，这可能不是摆脱它的正确方法，因为我猜自从最新的提交之前它仍然会尝试将其推出？
回答by Julio Daniel Reyes
According to github's help pagemax size per file is 100MB, and up to 1GB total for your repo.
根据github 的帮助页面，每个文件的最大大小为 100MB，您的存储库总共最多 1GB。
Are you using LFS?
你在使用LFS吗？
回答by DFBerry
I got this error, after cloning fresh from the upstream master, then I was pushing to my fork but had not kept my fork's master up to date with the upstream master. The different between the fork's master and what the new clone's upstream master had were too different.
我收到了这个错误，在从上游 master 克隆新鲜之后，我正在推送到我的叉子，但没有让我的叉子的 master 与上游 master 保持同步。分叉的主人和新克隆的上游主人的区别太大了。
The fix was to blow away my fork (copy all existing branches to my local computer so I don't loose any current work), refork, clone from my fork (not upstream), make changes on local computer, and push back to fork.
修复是吹走我的叉子（将所有现有分支复制到我的本地计算机，这样我就不会丢失任何当前的工作），重新分叉，从我的叉子（不是上游）克隆，在本地计算机上进行更改，然后推回叉子.
