Git/SmartGit 未能推动“大”发展文件
我正在使用 Smartgit 2.0.2。当我尝试推送小文件（例如 1kb .txt 文件）时，它可以工作。然而，对于 2mb 和 6mb 文件，它会失败。这是输出：
Commit: sha1 file '<stdout>' write error: Invalid argument The remote end hung up unexpectedly pack-objects died with strange error failed to push some refs to '<link hidden>'
[master 94d1218] test
1 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 Client/Leavers.pdf
sha1 file '<stdout>' write error: Invalid argument
The remote end hung up unexpectedly
pack-objects died with strange error
failed to push some refs to '<link hidden>'
在世界的另一端，使用不同的计算机、连接，但配置相同，一切正常。有人知道如何解决它，或者至少知道它是什么吗？先感谢您。
I am using Smartgit 2.0.2. When I try to push small file (for example 1kb .txt file) it works. However with 2mb and 6mb files it fails. Here's output:
Commit: sha1 file '<stdout>' write error: Invalid argument The remote end hung up unexpectedly pack-objects died with strange error failed to push some refs to '<link hidden>'
[master 94d1218] test
1 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 Client/Leavers.pdf
sha1 file '<stdout>' write error: Invalid argument
The remote end hung up unexpectedly
pack-objects died with strange error
failed to push some refs to '<link hidden>'
On other side of the world, with different computer, connection, but same configuration everything works correctly. Anyone have idea how to fix it, or what it is at least? Thank you in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Smartgit 在 UI 包装器下使用标准 git 命令行。问题是网络问题。尝试设置 SSH 密钥来与远程服务器通信。如果可以，请设置远程服务器（或让其系统管理员执行此操作），以便它为您的 SSH 设置设置 KeepAlive。这是通过其端的 sshd_config 完成的。您可能还需要调整您的 ssh_config （客户端）。有些服务器无法与不稳定的网络提供商很好地配合，因此即使是很小的网络故障也可能会导致连接中断，这在较长的下载过程中更有可能发生。 DSL 和过度使用的电缆子网是主要嫌疑人。
如果您需要有关 SSH keepalive 的更多信息，请查看我们的博客文章 http://www.cybersprocket.com /标签/ssh/
Smartgit uses a standard git command line under the UI wrappers. The problem is a network issue. Try setting up an SSH key to communicate with the remote server. If you can, set the remote server (or have their system admin do it) so that it sets the KeepAlive for your SSH setting. This is done via the sshd_config on their end. You may also need to tweak your ssh_config (the client side) on your end. Some servers don't play well with unstable network providers so even a small network hiccup can drop the connection, which is much more likely during a longer download. DSL and overused cable subnets are prime suspects.
IF you need more information on SSH keepalives, check out our blog articles at http://www.cybersprocket.com/tag/ssh/
使用 git 推送大文件时遇到同样的问题。在服务器上，auth.log 包含
输入时的 MAC 损坏，这似乎是 长期存在的已知内核错误。应用该页面上找到的修复ethtool -K eth0 rx off tx off后，问题得到解决。Had the same problem pushing big files with git. On the server, auth.log contained
Corrupted MAC on inputwhich seems to be a long standing known kernel bug. After applying the fix found on that pageethtool -K eth0 rx off tx offthe problem was resolved.