通道117无效-Eclipse/EGit

我正在使用最新版本的Eclipse（4.2.1）和EGit（2.3.1）将代码推送到位于Assembla的git存储库。最近我开始收到这样的信息：“117频道无效”。推的过程似乎很糟，所以并不真的痛，但很烦人，因为我看不到推的结果。 有什么想法吗？谢谢

错误日志：

An exception occurred during push on URI git@git.assembla.com:cool_awesome_app.git: Invalid channel 117
org.eclipse.jgit.api.errors.TransportException: Invalid channel 117
at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:157)
at org.eclipse.egit.core.op.PushOperation.run(PushOperation.java:215)
at org.eclipse.egit.ui.internal.push.PushOperationUI.execute(PushOperationUI.java:147)
at org.eclipse.egit.ui.internal.push.PushOperationUI$1.run(PushOperationUI.java:209)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: org.eclipse.jgit.errors.PackProtocolException: Invalid channel 117
at org.eclipse.jgit.transport.SideBandInputStream.needDataPacket(SideBandInputStream.java:175)
at org.eclipse.jgit.transport.SideBandInputStream.read(SideBandInputStream.java:136)
at org.eclipse.jgit.util.IO.readFully(IO.java:246)
at org.eclipse.jgit.transport.PacketLineIn.readLength(PacketLineIn.java:186)
at org.eclipse.jgit.transport.PacketLineIn.readString(PacketLineIn.java:138)
at org.eclipse.jgit.transport.BasePackPushConnection.readStringLongTimeout(BasePackPushConnection.java:352)
at org.eclipse.jgit.transport.BasePackPushConnection.readStatusReport(BasePackPushConnection.java:293)
at org.eclipse.jgit.transport.BasePackPushConnection.doPush(BasePackPushConnection.java:187)
at org.eclipse.jgit.transport.BasePackPushConnection.push(BasePackPushConnection.java:142)
at org.eclipse.jgit.transport.PushProcess.execute(PushProcess.java:141)
at org.eclipse.jgit.transport.Transport.push(Transport.java:1162)
at org.eclipse.jgit.api.PushCommand.call(PushCommand.java:153)
... 4 more

eclipse.buildId=M20130204-1200
java.version=1.6.0_43
java.vendor=Apple Inc.

---

我为Assembla工作，这是我们处理边带通信信道的方式中的一个问题，应该解决。奇怪的是，只有jgit/egit抱怨这一点，而不是git的c版本

---

请再次查看。

是否有堆栈跟踪，例如在错误日志视图中？顺便说一句，EGit的版本可能是2.3.1，而不是2.1.3，对吗？我对EGit版本2.2.0.201212191850-r也有同样的问题。我想知道这是否发生在早期版本的EGit上？似乎它不喜欢协商的通道，这就是为什么您没有显示结果的原因。@robinst 2.3.1确实，谢谢-我更正了它并添加了堆栈跟踪。如果其他人想跟踪它的进度，请链接到bug：