Community
Participate
Working Groups
I'm having trouble running a fetch operation against an https git repo after upgrading to 0.11. I tried resetting my credentials, clearing the secure store, etc… After downgrading to 0.10.1, fetch operations worked again. Here are some of the errors I was able to snag from the error log: org.eclipse.core.runtime.CoreException: <redacted>: not authorized at org.eclipse.egit.ui.internal.fetch.FetchOperationUI.execute(FetchOperationUI.java:102) at org.eclipse.egit.ui.internal.fetch.FetchOperationUI$1.run(FetchOperationUI.java:117) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.jgit.errors.TransportException: <redacted>: not authorized at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:385) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:215) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:125) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:111) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:903) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:134) at org.eclipse.egit.core.op.FetchOperation.run(FetchOperation.java:128) at org.eclipse.egit.ui.internal.fetch.FetchOperationUI.execute(FetchOperationUI.java:99) ... 2 more org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) Caused by: java.lang.NullPointerException at org.eclipse.egit.ui.internal.fetch.FetchResultDialog.<init>(FetchResultDialog.java:91) at org.eclipse.egit.ui.internal.fetch.FetchResultDialog$1$1.run(FetchResultDialog.java:72) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 23 more
I have tried this both in 0.10 and 0.11 for a newly created repo: remote.origin.url https://mathiaskinzler@github.com/mathiaskinzler/TestHttps.git Worked fine in both cases (using Eclipse network settings "Direct"). Any idea what could be different on your side?
(In reply to comment #1) > I have tried this both in 0.10 and 0.11 for a newly created repo: > > remote.origin.url > https://mathiaskinzler@github.com/mathiaskinzler/TestHttps.git > > Worked fine in both cases (using Eclipse network settings "Direct"). > > Any idea what could be different on your side? I just switch back to 0.11 and the problem still occurs. Does the test server require authentication or is it just https? Based on the error message, the issue seems to be with authentication. My eclipse was set to "native" network. I tried the other settings (manual and direct) and they had the same results.
(In reply to comment #2) > (In reply to comment #1) > > I have tried this both in 0.10 and 0.11 for a newly created repo: > > > > remote.origin.url > > https://mathiaskinzler@github.com/mathiaskinzler/TestHttps.git > > > > Worked fine in both cases (using Eclipse network settings "Direct"). > > > > Any idea what could be different on your side? > > I just switch back to 0.11 and the problem still occurs. Does the test server > require authentication or is it just https? Based on the error message, the > issue seems to be with authentication. > > My eclipse was set to "native" network. I tried the other settings (manual and > direct) and they had the same results. Also, the NPE seems bad...
(In reply to comment #2) > (In reply to comment #1) > > I have tried this both in 0.10 and 0.11 for a newly created repo: > > > > remote.origin.url > > https://mathiaskinzler@github.com/mathiaskinzler/TestHttps.git > > > > Worked fine in both cases (using Eclipse network settings "Direct"). > > > > Any idea what could be different on your side? > > I just switch back to 0.11 and the problem still occurs. Does the test server > require authentication or is it just https? Based on the error message, the > issue seems to be with authentication. > > My eclipse was set to "native" network. I tried the other settings (manual and > direct) and they had the same results. Yes, the test server requires authentication.
(In reply to comment #4) > (In reply to comment #2) > > (In reply to comment #1) > > > I have tried this both in 0.10 and 0.11 for a newly created repo: > > > > > > remote.origin.url > > > https://mathiaskinzler@github.com/mathiaskinzler/TestHttps.git > > > > > > Worked fine in both cases (using Eclipse network settings "Direct"). > > > > > > Any idea what could be different on your side? > > > > I just switch back to 0.11 and the problem still occurs. Does the test server > > require authentication or is it just https? Based on the error message, the > > issue seems to be with authentication. > > > > My eclipse was set to "native" network. I tried the other settings (manual and > > direct) and they had the same results. > > Yes, the test server requires authentication. Uhmm, sorry. It only requires authentication for push... Are you saying it needs authentication for fetch?
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > I have tried this both in 0.10 and 0.11 for a newly created repo: > > > > > > remote.origin.url > > > https://mathiaskinzler@github.com/mathiaskinzler/TestHttps.git > > > > > > Worked fine in both cases (using Eclipse network settings "Direct"). > > > > > > Any idea what could be different on your side? > > > > I just switch back to 0.11 and the problem still occurs. Does the test server > > require authentication or is it just https? Based on the error message, the > > issue seems to be with authentication. > > > > My eclipse was set to "native" network. I tried the other settings (manual and > > direct) and they had the same results. > > Also, the NPE seems bad... I pushed http://egit.eclipse.org/r/#change,2475 to avoid the NPE. It is not related to the authentication failure, however, so it is not a fix for this issue. I'll try to get hold of a repository that requires authentication for fetch.
(In reply to comment #6) > (In reply to comment #3) > > (In reply to comment #2) ... > > Also, the NPE seems bad... > > I pushed > > http://egit.eclipse.org/r/#change,2475 > > to avoid the NPE. It is not related to the authentication failure, however, so > it is not a fix for this issue. I'll try to get hold of a repository that > requires authentication for fetch. merged change 2475 as 226a7f50cdbff206855633bf85ed318375e95df4
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #3) > > > (In reply to comment #2) > ... > > > Also, the NPE seems bad... > > > > I pushed > > > > http://egit.eclipse.org/r/#change,2475 > > > > to avoid the NPE. It is not related to the authentication failure, however, so > > it is not a fix for this issue. I'll try to get hold of a repository that > > requires authentication for fetch. > > merged change 2475 as 226a7f50cdbff206855633bf85ed318375e95df4 Yes, our repository requires authentication for all operations.
Any ETA on this issue? I usually like to stay up-to-date with the latest updates of Eclipse plugins but I have to keep rejecting the stable update for egit and stay on 0.10 because the newer releases won't connect. Here is the new stack trace (no NPE now): org.eclipse.jgit.api.errors.JGitInternalException: Exception caught during execution of fetch command at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:138) at org.eclipse.jgit.api.PullCommand.call(PullCommand.java:217) at org.eclipse.egit.core.op.PullOperation$1.run(PullOperation.java:68) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1957) at org.eclipse.egit.core.op.PullOperation.execute(PullOperation.java:77) at org.eclipse.egit.ui.internal.repository.tree.command.PullCommand$1.run(PullCommand.java:66) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: org.eclipse.jgit.errors.TransportException: <redacted>: not authorized at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:385) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:215) at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:125) at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:111) at org.eclipse.jgit.transport.Transport.fetch(Transport.java:903) at org.eclipse.jgit.api.FetchCommand.call(FetchCommand.java:134) ... 7 more
Can you try the latest 0.11.3 release?
I just tried 0.11.3 and the latest nightly build just in case the fix was there. In both cases I get the same error about not being authorized. One thing I just noticed is that if I attempt to perform a pull after opening up Eclipse, it doesn't prompt for the password for the secure store. I don't think the credentials are even being queried for the fetch operation. I also tried to reset the fetch credentials and reconfigure fetch. Although reconfiguring fetch required me to type in my credentials (and worked), neither of these things seemed to fix the issue.
jgit commit e0a8398f1f167e4fceef7fa4ebbf413f16475e79 should fix that. Could you retry using the latest build [1] ? [1] https://hudson.eclipse.org/hudson/job/egit/lastSuccessfulBuild/artifact/org.eclipse.egit-updatesite/target/site/
Yup, works great, thanks!
