为什么git push会因为“操作超时”而失败？ [英] Why does git push fails with "Operation timed out"?

问题描述

  MacMini $ git push origin master 
计数对象：1916，完成。 
使用多达2个线程的增量压缩。 
压缩对象：100％（1751/1751），完成。 
从远程主机读取codebasehq.com：操作超时
致命：远程端意外挂起
错误：包对象因信号而死13 
错误：包对象死亡奇怪的错误
错误：未能将一些文件推送到'[e-mail]：xx / xx / xx.git'
  

$ b如果错误地识别流中的恶意软件，打包数据或不安全命令的痕迹，现代UTM防火墙可能会混淆外发数据......并且这些错误警报发生得非常频繁。您的网络或目的地端的这些安全设备可以解释为什么有些项目推得好，其他人正在放弃连接。

如果是这种情况，您可以避免触发如果您为此连接使用不同的协议，例如ssh：//或https：//而不是git：//。

MacMini $ git push origin master
Counting objects: 1916, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (1751/1751), done.
Read from remote host codebasehq.com: Operation timed out
fatal: The remote end hung up unexpectedly
error: pack-objects died of signal 13
error: pack-objects died with strange error
error: failed to push some refs to '[e-mail]:xx/xx/xx.git'

解决方案

Contemporary UTM firewalls can mess with outgoing data if they falsely identify traces of malware, packed data, or insecure commands in the stream... and these false alarms happen pretty frequently. Such security devices on your network or the destination side could explain why some projects push up okay and others are dropping the connection.

If that's the case, you may avoid the trigger if you use a different protocol for this connection, e.g. ssh:// or https:// instead of git://.

这篇关于为什么git push会因为“操作超时”而失败？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！