I did reach out to the one contact we had there from when GCP/Fastly were having issues that affected Travis/PyPI (Emma) on Monday, but got no response.
D. On Fri, May 18, 2018 at 8:54 AM, Sumana Harihareswara <s...@changeset.nyc> wrote: > In my opinion, this kind of bottleneck is likely to happen more frequently as > we increase PyPA development activity, so it'd be worth asking Travis to bump > up our account's oomph. (I am very tired and on a train so please forgive > handwavy wording.) Do we have a contact there? > > -- > Sumana Harihareswara > Changeset Consulting > https://changeset.nyc > > On 05/16/2018 04:36 PM, Dustin Ingram wrote: >> Thanks for the report. I reverted the commit that caused this in >> https://github.com/pypa/warehouse/pull/4015, however it might take a >> bit for this to get deployed to PyPI because there's currently a >> pretty long backlog in Travis due to all the PyPA development >> happening during the sprints. >> >> D. >> >> On Wed, May 16, 2018 at 4:28 PM, Alex Becker <alcubec...@gmail.com> wrote: >>> In the last hour I started observing the following loop: >>> >>> https://pypi.org/pypi/nonexistant-package/json -> >>> https://pypi.org/pypi/nonexistant-package/json/ -> >>> https://pypi.org/pypi/nonexistant-package/json >>> >>> This is breaking pipenv package resolution for us, since we use 2 different >>> indices and it checks for a 404 from PyPI before going on to the second one. >>> I assume any pipenv or pip user relying on multiple indices is currently >>> unable to resolve packages.
