Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 360095 - http://git.eclipse.org/c/?q=jdt doesn't respond
Summary: http://git.eclipse.org/c/?q=jdt doesn't respond
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Git (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 blocker with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-06 09:21 EDT by Olivier Thomann CLA
Modified: 2011-10-06 17:06 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Thomann CLA 2011-10-06 09:21:55 EDT
I cannot connect to this web ui http://git.eclipse.org/c/?q=jdt.
Also any git pull fails with this error:
$ git pull
error: Failed connect to git.eclipse.org:80; No error while accessing http://git.eclipse.org/c/jdt/eclipse.jdt.ui.git/info/refs

fatal: HTTP request failed
Comment 1 Remy Suen CLA 2011-10-06 09:29:53 EDT
Not being able to browse the web UI is a blocker for me also.
Comment 2 Brian de Alwis CLA 2011-10-06 09:34:37 EDT
Although I'm able to pull from the git server, I'm unable to open the web interface in my browser.
Comment 3 Brian de Alwis CLA 2011-10-06 09:38:14 EDT
Oh, perhaps I should note that I'm pulling from the smart server, not via http.
Comment 4 Olivier Thomann CLA 2011-10-06 09:57:08 EDT
Seems to be back online.
Comment 5 Eclipse Webmaster CLA 2011-10-06 10:04:54 EDT
We had a front line Apache process die in the night.  I've restarted it, and
will dig through the to see if I can work out what happened.

-M.
Comment 6 Olivier Thomann CLA 2011-10-06 10:11:31 EDT
Thanks for the quick response.
Comment 7 Denis Roy CLA 2011-10-06 11:36:05 EDT
You guys really should not be doing git operations (clone, pull) on the web front-end.  It is a dumb front-end and you're only causing yourselves unneeded pain.

Use the clone URLs at the bottom of the page instead.
Comment 8 Olivier Thomann CLA 2011-10-06 11:45:09 EDT
(In reply to comment #7)
> You guys really should not be doing git operations (clone, pull) on the web
> front-end.  It is a dumb front-end and you're only causing yourselves unneeded
> pain.
> 
> Use the clone URLs at the bottom of the page instead.
I don't do any operation directly on the web front end. I use it to make sure that the commits are properly done. Not being able to see what has been committed is an issue when working with git. This web front end is the only I found to do it.
Also I did the pull from the command line. And I cloned from Egit. Now sure there is anything else I can do.
Comment 9 Remy Suen CLA 2011-10-06 11:46:52 EDT
(In reply to comment #7)
> You guys really should not be doing git operations (clone, pull) on the web
> front-end.

Like Olivier, I do use those URLs but I like viewing individual branches in the web UI. I also use the web UI's commit links in my Bugzilla comments so that others can easily see the diff that I pushed to git.eclipse.org.

In any case, thanks for fixing this. :)
Comment 10 Denis Roy CLA 2011-10-06 17:06:52 EDT
IO may have misunderstood what you guys are doing.  It is possible to clone entire repos from cgit (the dumb web front-end at git.eclipse.org/c/ ) instead of using the http smart server (at git.eclipse.org/gitroot).

If that's not what you're doing, then please ignore my babbling.