[Catalog-sig] PyPI changelog API giving wrong results
donald.stufft at gmail.com
Wed Dec 19 03:39:13 CET 2012
On Tuesday, December 18, 2012 at 9:31 PM, Richard Jones wrote:
> Erk. PyPI host has significant clock error. NTP wasn't installed so I just did.
That sounds like it solves the ~15 minutes off issue, but the changelog being
off the system time shouldn't have affected that. I wasn't comparing to my
local time I was comparing to what PyPI was giving me via /daytime. So even
if the clock was 5 hours off /daytime and the changelog should have agreed.
> On 19 December 2012 00:14, Donald Stufft <donald.stufft at gmail.com (mailto:donald.stufft at gmail.com)> wrote:
> > PyPI is claiming that events are happening 5 hours prior
> > to when they actually occured.
> > See https://gist.github.com/4327695
> > The gist above illustrates grabbing the "current" time from
> > PyPI via /daytime, submitting a package, and then going
> > backwards in time 10 seconds at a time until we find when
> > PyPI claims this package was registered. It ended up
> > being 5 hours earlier than the "current" time grabbed
> > from PyPI.
> > (On a side note, the current time on /daytime is off by 15 minutes
> > or so).
> > _______________________________________________
> > Catalog-SIG mailing list
> > Catalog-SIG at python.org (mailto:Catalog-SIG at python.org)
> > http://mail.python.org/mailman/listinfo/catalog-sig
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Catalog-SIG