hi
going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today.
regards
On 19/06/17 12:39, Karanbir Singh wrote:
hi
going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today.
regards
Another brief outage coming today, sorry about the short notice.
On 22/06/17 14:11, Karanbir Singh wrote:
On 19/06/17 12:39, Karanbir Singh wrote:
hi
going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today.
regards
Another brief outage coming today, sorry about the short notice.
everything should be back now
On 22/06/17 16:08, Karanbir Singh wrote:
On 22/06/17 14:11, Karanbir Singh wrote:
On 19/06/17 12:39, Karanbir Singh wrote:
hi
going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today.
regards
Another brief outage coming today, sorry about the short notice.
everything should be back now
we're having some load issues, git.c.o might be down intermittently, I'll post once this is fixed.
On 22/06/17 16:48, Karanbir Singh wrote:
On 22/06/17 16:08, Karanbir Singh wrote:
On 22/06/17 14:11, Karanbir Singh wrote:
On 19/06/17 12:39, Karanbir Singh wrote:
hi
going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today.
regards
Another brief outage coming today, sorry about the short notice.
everything should be back now
we're having some load issues, git.c.o might be down intermittently, I'll post once this is fixed.
should be back, again. Service is going to be a bit slow - were getting hit quite hard, and the cache's are rebuilding.
On 06/22/2017 11:25 AM, Karanbir Singh wrote:
On 22/06/17 16:48, Karanbir Singh wrote:
On 22/06/17 16:08, Karanbir Singh wrote:
On 22/06/17 14:11, Karanbir Singh wrote:
On 19/06/17 12:39, Karanbir Singh wrote:
hi
going to be doing some non-disruptive maintenance work on git.centos.org later today, should not last more than 30 min, starting from 15:00 UTC today.
regards
Another brief outage coming today, sorry about the short notice.
everything should be back now
we're having some load issues, git.c.o might be down intermittently, I'll post once this is fixed.
should be back, again. Service is going to be a bit slow - were getting hit quite hard, and the cache's are rebuilding.
https://git.centos.org/blob/centos-git-common.git/master/centos.git.repolist...
No longer appears to work following the outage:
Traceback (most recent call last): File "./centos.git.repolist.py", line 73, in <module> main() File "./centos.git.repolist.py", line 68, in main repos = get_repo_list(url=options.url, branch=options.branch, projectpath=options.project) File "./centos.git.repolist.py", line 52, in get_repo_list repos = json.loads(payload) File "/usr/lib64/python2.7/site-packages/simplejson/__init__.py", line 516, in loads return _default_decoder.decode(s) File "/usr/lib64/python2.7/site-packages/simplejson/decoder.py", line 374, in decode obj, end = self.raw_decode(s) File "/usr/lib64/python2.7/site-packages/simplejson/decoder.py", line 404, in raw_decode return self.scan_once(s, idx=_w(s, idx).end()) simplejson.scanner.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
Pat
On Fri, Jun 23, 2017 at 6:15 AM, Pat Riehecky riehecky@fnal.gov wrote:
https://git.centos.org/blob/centos-git-common.git/master/centos.git.repolist...
No longer appears to work following the outage:
I saw a conversation on IRC #centos-devel about the following line:
RPCURL = "https://git.centos.org/rpc?req=LIST_REPOSITORIES"
You now need to add a "/" after the "rpc" like:
https://git.centos.org/rpc/?req=LIST_REPOSITORIES
Akemi
On 23/06/17 17:56, Akemi Yagi wrote:
You now need to add a "/" after the "rpc" like:
Indeed, all upstream examples now contain the trailing slash (which is how I got the idea of trying that out in the first place). [1]
Karanbir was thinking yesterday about adding a redirection so that the old URLs keep working. I suspect the root cause could be a change in Tomcat, but it can be configured to automatically add the trailing slash, if missing. [2] Maybe this would be better than HTTP redirects, as it would need fewer requests.
Regards, Laurențiu
[1] http://gitblit.com/rpc.html [2] https://stackoverflow.com/a/34400627
On 23/06/17 17:36, Laurentiu Pancescu wrote:
On 23/06/17 17:56, Akemi Yagi wrote:
You now need to add a "/" after the "rpc" like:
Indeed, all upstream examples now contain the trailing slash (which is how I got the idea of trying that out in the first place). [1]
Karanbir was thinking yesterday about adding a redirection so that the old URLs keep working. I suspect the root cause could be a change in Tomcat, but it can be configured to automatically add the trailing slash, if missing. [2] Maybe this would be better than HTTP redirects, as it would need fewer requests.
i had a brief look this morning, there are quite a few implications of a generic redirect like that.
On 23/06/17 19:00, Karanbir Singh wrote:
Indeed, all upstream examples now contain the trailing slash (which is how I got the idea of trying that out in the first place). [1]
Karanbir was thinking yesterday about adding a redirection so that the old URLs keep working. I suspect the root cause could be a change in Tomcat, but it can be configured to automatically add the trailing slash, if missing. [2] Maybe this would be better than HTTP redirects, as it would need fewer requests.
i had a brief look this morning, there are quite a few implications of a generic redirect like that.
"curl -I https://git.centos.org/rpc?req=LIST_REPOSITORIES" still produces a 404 for me right now, while the version with the slash works. Anyway, the 404 page contains a "Powered by Jetty" banner, so it probably doesn't matter what Tomcat would do. I thought Jetty would add a trailing slash by default - apparently not...
Regards, Laurențiu
On 23/06/17 16:56, Akemi Yagi wrote:
On Fri, Jun 23, 2017 at 6:15 AM, Pat Riehecky riehecky@fnal.gov wrote:
https://git.centos.org/blob/centos-git-common.git/master/centos.git.repolist...
No longer appears to work following the outage:
I saw a conversation on IRC #centos-devel about the following line:
RPCURL = "https://git.centos.org/rpc?req=LIST_REPOSITORIES"
You now need to add a "/" after the "rpc" like:
The original URL that Pat complained about now seems to be working (for me at least). It also doesn't have an /rpc? in it to insert a / into.
Trevor
Hi Pat,
On 23/06/17 15:15, Pat Riehecky wrote:
https://git.centos.org/blob/centos-git-common.git/master/centos.git.repolist...
Traceback (most recent call last): File "./centos.git.repolist.py", line 73, in <module> main() File "./centos.git.repolist.py", line 68, in main repos = get_repo_list(url=options.url, branch=options.branch, projectpath=options.project) File "./centos.git.repolist.py", line 52, in get_repo_list repos = json.loads(payload) File "/usr/lib64/python2.7/site-packages/simplejson/__init__.py", line 516, in loads return _default_decoder.decode(s) File "/usr/lib64/python2.7/site-packages/simplejson/decoder.py", line 374, in decode obj, end = self.raw_decode(s) File "/usr/lib64/python2.7/site-packages/simplejson/decoder.py", line 404, in raw_decode return self.scan_once(s, idx=_w(s, idx).end()) simplejson.scanner.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
I was a bit confused why I see a JSON decoder exception when the server returns a 404 status. There's a try block there, but python-requests doesn't raise an exception on HTTP error codes by default. May I suggest either explicitly checking req.status_code against 200 before parsing, or adding a call to req.raise_for_status() to the try block? This would better handle such errors for the future, and would have pointed you from the beginning in the right direction.
Best regards, Laurențiu