git: error pushing via HTTP (return code 22)

If you get a error: Cannot access URL http://github.com/xxxxxxx/, return code 22 when trying to push changes to a git repository via HTTP. This is probably because you are using an HTTP proxy to access the repo and that proxy doesn’t support WebDAV HTTP methods (especially PROPFIND). So when git issues a PROPFIND the http proxy answers back with a 500 Internal Server Error or something like that. It seems that PROPFIND is absolutely required so if you can use git:// directly or use a HTTP proxy which supports PROPFIND. Then I think the only option left is try use CONNECT in the proxy.

September 23, 2009

Eclipse Error Reporting: Exception stacktrace details

I’m working with Eclipse 3.2.2 RCP right now and I’m getting an exception that I want to display on screen. I found in the eclipsepedia that we must use ErrorDialog to report errors: try { // ... } catch (InvocationTargetException e) { IStatus status = new Status(IStatus.ERROR, Application.ID, 1, "Exception found.", e.getCause()); ErrorDialog.openError(window.getShell(),"Error while loading file", null,status); } But using this code snippet will only print the e.getLocalizedMessage() in the Details pane of the ErrorDialog. See screenshot ...

July 25, 2007

cvs [xxxxx]: received broken pipe signal

Today I received this error message when issuing a cvs import to the cvs repository cvs [import failed]: received broken pipe signal after googling a little bit I found this mail thread that led me to the following entry in the cvs manual about loginfo: Note that the filter program must read all of the log information or CVS may fail with a broken pipe signal. so I took a look to the CVSROOT/loginfo and the line there was ...

March 29, 2007