GitHub,推送错误:远端意外挂断 [英] GitHub, push error: the remote end hung up unexpectedly

查看:369
本文介绍了GitHub,推送错误:远端意外挂断的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我现在无法将本地提交推送到github存储库.我收到一条错误消息:

Counting objects: 76, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (75/75), done.
Writing objects: 100% (76/76), 5.23 MiB | 24.67 MiB/s, done.
Total 76 (delta 45), reused 0 (delta 0)
remote: fatal: early EOF
error: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 32
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

我尝试了此处提供的一些解决方案,什么都行不通.

我还试图推动另一个项目以排除网络问题.尽管花了一些时间,它还是成功了.

我跑了git fsck,收到了

git fsck --full
Checking object directories: 100% (256/256), done.
Checking objects: 100% (3831/3831), done.

解决方案


文件大小

让我们尝试使用更大的帖子缓冲区,如此处所述

git config http.postBuffer 100000000

http.postBuffer

将数据POST到远程系统时,智能HTTP传输使用的缓冲区的最大大小(以字节为单位).对于大于此缓冲区大小的请求,将使用HTTP/1.1和Transfer-Encoding:chunked来避免在本地创建大型打包文件.默认值为1 MiB,足以应付大多数请求.

来自 https://stackoverflow.com/a/3605544/581076

想法/p>


原始思想

这看起来像是服务器问题.

如果您以前可以进行推送,建议您再等一段时间再尝试.

I now cannot push my local commit to the github repo. I received an error message:

Counting objects: 76, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (75/75), done.
Writing objects: 100% (76/76), 5.23 MiB | 24.67 MiB/s, done.
Total 76 (delta 45), reused 0 (delta 0)
remote: fatal: early EOF
error: RPC failed; curl 55 SSL_write() returned SYSCALL, errno = 32
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I've tried some solutions offered here, nothing works.

I also tried to push another project to rule out network issue. It succeeded, although taking some time.

I ran git fsck, receiving

git fsck --full
Checking object directories: 100% (256/256), done.
Checking objects: 100% (3831/3831), done.

解决方案


File size

Let's try with a bigger post buffer as described here.

git config http.postBuffer 100000000

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.

Idea from https://stackoverflow.com/a/3605544/581076


Original thought

This looks like a server issue.

If you have been able to push before, I suggest trying again after waiting some more time.

这篇关于GitHub,推送错误:远端意外挂断的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆