Heh. That wasn't apparent to me at all. But yeah, the 503 still
indicates that fastly had trouble reaching the server. It's almost
certainly Rackspace's restarts that caused this.
On Tue, Mar 3, 2015 at 8:09 AM, Reinout van Rees <reinout(a)vanrees.org> wrote:
> Ian Cordasco schreef op 03-03-15 om 14:52:
> If bootstrap.pypa.io sits behind fastly, a 503 would indicate that it
> couldn't reach the server. That means that it is either exactly what Nick
> pointed out or a semi-normal error from fastly. There's a reason pip retries
> package downloads when it sees a 503 response status code.
> Well, it wasn't a temporary one-second hickup. It was down for a couple of
> hours this morning. ("morning" = "morning in Europe" :-) ).
> Reinout van Rees http://reinout.vanrees.org/
> reinout(a)vanrees.org http://www.nelen-schuurmans.nl/
> "Learning history by destroying artifacts is a time-honored atrocity"
I'm getting a "503 service unavailable" on https://bootstrap.pypa.io/
This effectively kills all "bootstrap.py" scripts of our buildouts :-(
Where is the best place to report this, normally? I looked at the pypi
bug tracker but didn't see a mention of pypa.io there.
Reinout van Rees http://reinout.vanrees.org/
"Learning history by destroying artifacts is a time-honored atrocity"