I'm using the latest versions of Eclipse (4.2.1) and EGit (2.3.1) to push code to git repositories that are hosted at Assembla. Lately I start getting those messages: "Invalid channel 117". The push seems to go trough, so it doesn't really hurt, but it's annoying because I cannot see the result of the push.
Any ideas? Thanks!
Error Log:
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.
I work for Assembla, this was a problem in the way we were handling sideband communication channels - it should be fixed. Oddly only jgit/egit complained about this and not the c version of git.
Please take a look again.
Related
During a multimodule build, an error is surfaced in eclipse as follows:
Execution default of goal org.apache.maven.plugins:maven-war-plugin:3.3.1:exploded failed. (org.apache.maven.plugins:maven-war-plugin:3.3.1:exploded:default:process-resources)
The stack trace for this error is
org.apache.maven.plugin.PluginExecutionException: Execution default of goal org.apache.maven.plugins:maven-war-plugin:3.3.1:exploded failed.
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:148)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:332)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.lambda$8(MavenImpl.java:1380)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:114)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1379)
at org.eclipse.m2e.core.project.configurator.MojoExecutionBuildParticipant.build(MojoExecutionBuildParticipant.java:54)
at org.eclipse.m2e.core.internal.builder.MavenBuilderImpl.build(MavenBuilderImpl.java:135)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:169)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$1.method(MavenBuilder.java:1)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$1(MavenBuilder.java:114)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:114)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.lambda$0(MavenBuilder.java:105)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:179)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:153)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:101)
at org.eclipse.m2e.core.internal.builder.MavenBuilder$BuildMethod.execute(MavenBuilder.java:88)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:197)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:832)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:220)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:263)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:316)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:319)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:371)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:392)
at org.eclipse.core.internal.resources.Workspace.buildInternal(Workspace.java:515)
at org.eclipse.core.internal.resources.Workspace.build(Workspace.java:405)
at org.eclipse.ui.actions.GlobalBuildAction$1.run(GlobalBuildAction.java:180)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.lang.NullPointerException
at org.apache.maven.plugins.war.AbstractWarMojo$DefaultWarPackagingContext$1.visitFile(AbstractWarMojo.java:661)
at org.apache.maven.plugins.war.AbstractWarMojo$DefaultWarPackagingContext$1.visitFile(AbstractWarMojo.java:656)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2804)
at java.base/java.nio.file.Files.walkFileTree(Files.java:2876)
at org.apache.maven.plugins.war.AbstractWarMojo$DefaultWarPackagingContext.<init>(AbstractWarMojo.java:655)
at org.apache.maven.plugins.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:520)
at org.apache.maven.plugins.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:453)
at org.apache.maven.plugins.war.WarExplodedMojo.execute(WarExplodedMojo.java:43)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
... 31 more
pom.xml /my-legacy-app line 1753 Maven Build Problem
I've debugged into AbstractWarMojo.visitFile, and there session.getStartTime() is null, so the call to getTime() throws an NPE.
Attempting to track down why the start time is null led me to MavenImpl, at which point I've gotten a bit stuck trying to
further track down the issue. I think it was pointing to something in MavenExecutionContext, but I'm not entirely sure.
How do I go about solving this problem?
Eclipse Version: 20200910-1200
m2e Version: 1.16.1.20200710-1008
This was due to code introduced in version 3.3.1 of the maven-war-plugin, using 3.3.0 solves the problem.
I've install eclipse kepler Java Developer EE and install ZK Studio throung Market place. But Errors Appear :
An error occurred while collecting items to be installed session
context was
:(profile=epp.package.jee, phase=org. eclipse. equinox. internal. p2.
engine.phases.Collect, operand=, action=). Unable to read repository
at studio. zkoss
.org/resource/plugins/eclipse42/plugins/org.zkoss.eclipse.editor2.0.1.v201312091448.jar.
Premature end of Content-Length delimited message body (expected:
5833581; received: 5816781 Unable to read repository at
http://studio.zkoss.org/resource/plugins/eclipse42/plugins/org.zkoss.eclipse.pack2.0.1.v201312091448.jar.
Premature end of Content-Length delimited message body (expected:
7912681; received: 7874881 Unable to read repository at
http://studio.zkoss.org/resource/plugins/eclipse42/plugins/org.zkoss.eclipse.setting2.0.1.v201312091448.jar.
Premature end of Content-Length delimited message body (expected:
779524; received: 778124 Unable to read repository at
http://studio.zkoss.org/resource/plugins/eclipse42/plugins/org.zkoss.eclipse.zks2.0.1.v201312091448.jar.
Premature end of Content-Length delimited message body (expected:
2501827; received: 2496227
What should I do to solve this problem and continue install ZK Studio?
I've solved the problem. I check my firewall it turn out the firewall is enabled. so I disabled the firewall and continue install zk.
Thanks,
Dian
I have installed eclipse Luna and i try to checkout existing branch from the bitbucket through eclipse(file->import->GIT->Projects from GIT). In the branch selection screen, i got the following error:
!MESSAGE https://test#bitbucket.org/test/eclipse.git 407 Proxy Authentication Required
!STACK 0
org.eclipse.jgit.api.errors.TransportException: https://test#bitbucket.org/test/eclipse.git 407 Proxy Authentication Required
at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:223)
at org.eclipse.jgit.api.LsRemoteCommand.call(LsRemoteCommand.java:159)
at org.eclipse.egit.core.op.ListRemoteOperation.run(ListRemoteOperation.java:99)
at org.eclipse.egit.ui.internal.clone.SourceBranchPage$8.run(SourceBranchPage.java:339)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
I have set proxy through window -> network connection -> manual option and added following code in eclipse ini:
-vmargs
-Dorg.eclipse.ecf.provider.filetransfer.excludeContributors=org.eclipse.ecf.provider.filetransfer.httpclient4
-Dhttp.proxyHost=192.168.2.55
-Dhttp.proxyPort=3128
-Dhttps.proxyHost=192.168.2.55
-Dhttps.proxyPort=3128
-DsocksProxyHost=
-DsocksProxyPort=
-Dhttp.proxyUser=proxy
-Dhttp.proxyPassword=proxyss4u
-Dhttp.nonProxyHosts=localhost|127.0.0.1
-Dorg.eclipse.equinox.p2.transport.ecf.retry=5
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.connectTimeout=15000
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.readTimeout=1000
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.retryAttempts=20
-Dorg.eclipse.ecf.provider.filetransfer.retrieve.closeTimeout=1000
-Dorg.eclipse.ecf.provider.filetransfer.browse.connectTimeout=3000
-Dorg.eclipse.ecf.provider.filetransfer.browse.readTimeout=1000
But still i got the 407 Proxy Authentication Required issue.
Kindly advice us.
Has anyone seen the following exception from Jenkins?
FATAL: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-Push Notifications API (Master)-3 is invalid
hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-Push Notifications API (Master)-3 is invalid
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:179)
at hudson.plugins.git.GitAPI.tag(GitAPI.java:220)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1239)
at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196)
at hudson.FilePath.act(FilePath.java:865)
at hudson.FilePath.act(FilePath.java:838)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1353)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594)
at hudson.model.Run.execute(Run.java:1567)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:237)
Caused by: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-Push Notifications API (Master)-3 is invalid
at org.eclipse.jgit.api.TagCommand.processOptions(TagCommand.java:198)
at org.eclipse.jgit.api.TagCommand.call(TagCommand.java:112)
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:175)
... 14 more
This is a Scala project and we are using SBT 12.1 to build it. My googling has only returned issues with older versions of Jenkins which I am past. We have 1.506.
We have a ton of other projects building just fine and some of them are also Scala.
I got this error building a Java project. I'm not sure why this would suddenly crop up, but I was able to work around it by doing the following:
Go to the Advanced... config settings for the Source Code Management section of the build config and check "Skip Internal Tag".
(upgraded from comment)
On Eclipse Galileo, got the following ClassNotFoundException when doing Debug As/Web Application. But works just fine when doing Run As/Web Application.
I was given message that "The source attachment does not contain the source for the file URLClassLoader.class. You can change the source attachment by clicking the Change Attached Source below:"
In the project window, it seems that the URLClassLoader class is from Java.net package, which is from /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Classes/classes.jar.
I found the jar on the machine, what else I am missing? why it's debug only issue?
Could it be possible that the JRE system library that I have on my iMac 10.6.5 machine is outdated? Or somehow install/unstall of some jar/package caused the issue?
This is what I have - JRE System Library [JVM 1.6.0 (MacOS X Default)] - would update it help fixing the issue? but how to get it updated?
Please help!
com.google.appengine.tools.development.DevAppServerMain at localhost:57873
Thread [main] (Suspended (exception ClassNotFoundException))
Launcher$ExtClassLoader(URLClassLoader).findClass(String) line: 207
Launcher$ExtClassLoader.findClass(String) line: 229
Launcher$ExtClassLoader(ClassLoader).loadClass(String, boolean) line: 307
Launcher$AppClassLoader(ClassLoader).loadClass(String, boolean) line: 296
Launcher$AppClassLoader.loadClass(String, boolean) line: 301
Launcher$AppClassLoader(ClassLoader).loadClass(String) line: 248
InstrumentationImpl.loadClassAndStartAgent(String, String, String) line: 280
InstrumentationImpl.loadClassAndCallPremain(String, String) line: 338
/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/bin/java (Nov 30, 2010 9:40:41 PM)
Perhaps you need to install JDK which has complete sources? Refer to Apple website to download the latest JDK, might need an Apple ID.
After that change eclipse's java runtime accordingly to use the new installed JDK:
And re-build your project: Project -> Source -> Clean-up