My Commit and Push from my STS Eclipse to Bitbucket worked fine the last year. I don't change anything there but today I get the following error:
Does anyone why?
If I make a pull I geht the following exception:
Actually I dont know what to do, I have not changed anything concerning git in the last half year.
[EDIT]
I have installed this Eclipse Bundles:
I think this is the problem:
The POM for org.crashub:crash.shell:jar:1.3.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
Does anyone know how to solve this issue?
[EDIT2]
I have installed the new version of STS (3.7.2) and Iam also getting the same Exception:
org.eclipse.jgit.api.errors.TransportException: invalid advertisement of
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.components.RefSpecPage$3.run(RefSpecPage.java:254)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
Caused by: org.eclipse.jgit.errors.PackProtocolException: invalid advertisement of
at org.eclipse.jgit.transport.TransportHttp$HttpObjectDB.invalidAdvertisement(TransportHttp.java:746)
at org.eclipse.jgit.transport.TransportHttp$HttpObjectDB.readAdvertisedImpl(TransportHttp.java:712)
at org.eclipse.jgit.transport.TransportHttp.newDumbConnection(TransportHttp.java:328)
at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:306)
at org.eclipse.jgit.api.LsRemoteCommand.execute(LsRemoteCommand.java:202)
... 4 more
With Git Bash it still works fine. Does anyone have any idea how I can sole this?
Related
I can use git fine from command line, I can use fine git from NetBeans IDE, and I can use git fine from IntelliJ IDEA.
But I cannot use git in any instance of Eclipse (either pure Eclipse for Java IDE, or IBM Rational Application Developer which based on Eclipse). SSH keys configured same as for other IDEs and are valid.
I suspect problem at some OS level, maybe Eclipse stores some global settings somewhere and all instance reuse them. Tried to delete %USERPROFILE%/.eclipse -- did not help.
The error in .log is like that (again, keys are valid and properly configured in SSH2 Preferences dialog in Eclipse):
!ENTRY org.eclipse.egit.ui 4 0 2019-03-29 13:01:45.024
!MESSAGE git#git.assembla.com:xxx.git: git#git.assembla.com: Permission denied (publickey,keyboard-interactive).
!STACK 0
org.eclipse.jgit.api.errors.TransportException: git#git.assembla.com:xxx.git: git#git.assembla.com: Permission denied (publickey,keyboard-interactive).
[UPDATED on 04/02/19]
as you can see github.com was not even added to known hosts, i.e. it was not attempted to connect.
typical error.
command line git works
adding user id git to ssh protocol connection type does not help.
Ok, playing with Visual Studio Code I stumbled on the same problem and was able to fix it, so I tried to apply solution to Eclipe and it started working for me.
Not sure why the original problem started, but now I found at least a workaround and can use Git from the Eclipse.
To remind what I had in Eclipse:
org.eclipse.core.runtime.CoreException: Invalid remote: origin
at org.eclipse.egit.ui.internal.fetch.FetchOperationUI.execute(FetchOperationUI.java:106)
at org.eclipse.egit.ui.internal.fetch.FetchOperationUI$1.runInWorkspace(FetchOperationUI.java:123)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: origin
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:136)
at org.eclipse.egit.core.op.FetchOperation.run(FetchOperation.java:134)
at org.eclipse.egit.ui.internal.fetch.FetchOperationUI.execute(FetchOperationUI.java:103)
... 3 more
Caused by: org.eclipse.jgit.errors.NoRemoteRepositoryException: git XXXXXXXXXXXXXXXXXXX: Permission denied (publickey).
at org.eclipse.jgit.transport.TransportGitSsh.cleanNotFound(TransportGitSsh.java:208)
at org.eclipse.jgit.transport.TransportGitSsh$SshFetchConnection.(TransportGitSsh.java:288)
at org.eclipse.jgit.transport.TransportGitSsh.openFetch(TransportGitSsh.java:161)
at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:136)
at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:122)
at org.eclipse.jgit.transport.Transport.fetch(Transport.java:1138)
at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:130)
The solution was to start SSH agent first (to avoid asking passphrase) and then in the same shell session start Eclipse. Without any changes in Eclipse error gone and IDE started reaching repository.
So, the steps would be:
Open shell session (cmd.exe)
Start SSH agent (start-ssh-agent.cmd)
[In the same shell session] Start Eclipse (eclipse.exe)
I got update notification from Sprint Tool Suite or STS. I updated the packages as it asked for and did not pay attention to what exactly got updated. After the update, remote git operations i.e. push/pull are failing with following error. Git integration was working fine before the update and git commands do work properly from command line. STS still shows repository name and does recognize that project is connected to git
Can't connect to any repository: user#server:repository
(user#server:repository: connection failed)
I see following error getting logged in .log file of the workspace
org.eclipse.jgit.api.errors.TransportException:
user#server:repository: connection failed at
org.eclipse.jgit.api.PushCommand.call(PushCommand.java:180) at
org.eclipse.egit.core.op.PushOperation.run(PushOperation.java:215) at
org.eclipse.egit.ui.internal.push.PushJob.performJob(PushJob.java:84)
at
org.eclipse.egit.ui.internal.jobs.RepositoryJob.run(RepositoryJob.java:57)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused
by: org.eclipse.jgit.errors.TransportException:
user#server:repository: connection failed at
org.eclipse.jgit.transport.JschSession$JschProcess.(JschSession.java:156)
at org.eclipse.jgit.transport.JschSession.exec(JschSession.java:92)
at
org.eclipse.jgit.transport.TransportGitSsh$SshPushConnection.(TransportGitSsh.java:332)
at
org.eclipse.jgit.transport.TransportGitSsh.openPush(TransportGitSsh.java:174)
at
org.eclipse.jgit.transport.PushProcess.execute(PushProcess.java:160)
at org.eclipse.jgit.transport.Transport.push(Transport.java:1310) at
org.eclipse.jgit.api.PushCommand.call(PushCommand.java:169) ... 4
more
Spring Tool Suite
Version: 3.9.1.RELEASE
Build Id: 201710111144
Platform: Eclipse Neon.3 (4.6.3)
I have a similar problem since the updates, but running on Eclipse Oxygen 1a.
I've created an issue with Spring Ide.
https://github.com/spring-projects/spring-ide/issues/210
While Developing Project I got this Error.I used Eclipse Mars and Tomcat v8.0 Server.Actually upto last Night it works good but next morning it shows this error block.Nothing to be displayed in console, Error is just display on pop up window.I didn't get proper solution,So please help me to solve this error
java.lang.NullPointerException
at org.eclipse.jst.common.internal.modulecore.IgnoreJavaInSourceFolderParticipant.shouldAddExportableFile(IgnoreJavaInSourceFolderParticipant.java:64)
at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.shouldAddComponentFile(FlatVirtualComponent.java:288)
at org.eclipse.wst.common.componentcore.internal.flat.VirtualComponentFlattenUtility.addFile(VirtualComponentFlattenUtility.java:122)
at org.eclipse.wst.common.componentcore.internal.flat.VirtualComponentFlattenUtility.addMembersInternal(VirtualComponentFlattenUtility.java:99)
at org.eclipse.wst.common.componentcore.internal.flat.VirtualComponentFlattenUtility.addMembersInternal(VirtualComponentFlattenUtility.java:96)
at org.eclipse.wst.common.componentcore.internal.flat.VirtualComponentFlattenUtility.addMembers(VirtualComponentFlattenUtility.java:51)
at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.treeWalk(FlatVirtualComponent.java:230)
at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:188)
at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:118)
at org.eclipse.wst.web.internal.deployables.FlatComponentDeployable.members(FlatComponentDeployable.java:227)
at org.eclipse.jst.j2ee.internal.deployables.J2EEFlexProjDeployable.members(J2EEFlexProjDeployable.java:267)
at org.eclipse.wst.server.core.internal.ModulePublishInfo.fillCache(ModulePublishInfo.java:314)
at org.eclipse.wst.server.core.internal.ModulePublishInfo.getDelta(ModulePublishInfo.java:396)
at org.eclipse.wst.server.core.internal.ServerPublishInfo.getDelta(ServerPublishInfo.java:366)
at org.eclipse.wst.server.core.internal.Server.getPublishedResourceDelta(Server.java:1578)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.getPublishedResourceDelta(ServerBehaviourDelegate.java:698)
at org.eclipse.jst.server.tomcat.core.internal.TomcatServerBehaviour.getPublishedResourceDelta(TomcatServerBehaviour.java:958)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.computeDelta(ServerBehaviourDelegate.java:874)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:909)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3172)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I had this issue as well, it turns out that for some reason Windows (or me) had made the Tomcat publish folder read only. I just removed that and the problem were solved.
I am new to using SVN, and I am trying it out on an android project. I am getting a commit failure based on this error..
svn: E155023: Can't set properties on 'C:\AndroidWorkSpace\myApp\bin\res': invalid status for updating properties.
I have searched for similar problems, but the lingo is all over my head. I just installed SVN on eclipse (it has successfully updated/committed previously), and I opened a repository on cloudforge.com. Other than that, I don't know much about it.
I have tried cleaning project and running team>clean up.
Here is the description of the bug, which might cause this error:
http://subversion.tigris.org/issues/show_bug.cgi?id=4004
Hope that helps!
We have a git repository managed by gitosis under Ubuntu, which has worked well all up to the disk ran full. After reading up a bit on the issue, I found that git gc and git gc --aggresive got me quite a bit of diskspace back. Very nice.
Unfortunately this appears to have broken something in egit, as I get this message when trying to clone our repository (during the checkout phase at around 10%)
Packfile corruption detected: Unknown
zlib error.
Interestingly enough the git in msysgit works just fine as before.
I tried upgrading egit to the nightly build of 0.12 as there was some mailing list messages hinting this had been fixed within the last week, but to no avail.
My question now is, what can I do to my repository to get to a state where egit works again? I have full control over the Ubuntu instance running gitosis.
EDIT: I got a stack trace from the Eclipse event log
org.eclipse.jgit.errors.TransportException: Packfile corruption detected: Unknown zlib error.
at org.eclipse.jgit.transport.BasePackFetchConnection.doFetch(BasePackFetchConnection.java:287)
at org.eclipse.jgit.transport.BasePackFetchConnection.fetch(BasePackFetchConnection.java:225)
at org.eclipse.jgit.transport.FetchProcess.fetchObjects(FetchProcess.java:214)
at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:149)
at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:111)
at org.eclipse.jgit.transport.Transport.fetch(Transport.java:903)
at org.eclipse.egit.core.op.CloneOperation.doFetch(CloneOperation.java:228)
at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:135)
at org.eclipse.egit.ui.internal.clone.GitCloneWizard.executeCloneOperation(GitCloneWizard.java:259)
at org.eclipse.egit.ui.internal.clone.GitCloneWizard.access$3(GitCloneWizard.java:252)
at org.eclipse.egit.ui.internal.clone.GitCloneWizard$4.run(GitCloneWizard.java:233)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.eclipse.jgit.errors.CorruptObjectException: Packfile corruption detected: Unknown zlib error.
at org.eclipse.jgit.transport.PackParser$InflaterStream.read(PackParser.java:1530)
at org.eclipse.jgit.transport.PackParser$InflaterStream.skip(PackParser.java:1500)
at org.eclipse.jgit.util.IO.skipFully(IO.java:203)
at org.eclipse.jgit.transport.PackParser.inflateAndSkip(PackParser.java:1352)
at org.eclipse.jgit.transport.PackParser.indexOneObject(PackParser.java:834)
at org.eclipse.jgit.transport.PackParser.parse(PackParser.java:448)
at org.eclipse.jgit.storage.file.ObjectDirectoryPackParser.parse(ObjectDirectoryPackParser.java:178)
at org.eclipse.jgit.transport.PackParser.parse(PackParser.java:410)
at org.eclipse.jgit.transport.BasePackFetchConnection.receivePack(BasePackFetchConnection.java:649)
at org.eclipse.jgit.transport.BasePackFetchConnection.doFetch(BasePackFetchConnection.java:280)
... 11 more
Edit: Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=340305
One way to get a clone without EGit is to:
make a bundle on the server
copy the unique file representing that bundle on the client side
try to clone it in command-line.
Since you mention you can process the bundle with msysgit, that suggests a bug on the Egit or JGit side, as illustrated by bug 330758.
The usual course of action is to update to the nightly latest fo EGit, using this p2 update site, and see if the problem is still there.
If the issue persists, you can then file a bug report or complete the existing one (330758).
Please check the versions of Git you are running and make sure they match.
The latest egit 0.12 does not show this behaviour.
Hopefully the bug has been fixed for real, and not just an accidental side effect.