365 days json file (non-min) is empty at the moment

Question

365 days json file (non-min) is empty at the moment

zahirtezcan-bugs opened this issue 5 years ago · comments

zahirtezcan-bugs commented 5 years ago

The this commit emptied the 365days file. 30 days file seems ok though.

Hugo van Kemenade · Answer 1 · Wed Apr 17 2019 15:18:01 GMT+0800 (China Standard Time)

Thanks for the report!

Checking the logs, it had exceeded the quota after fetching the 30-day file because I had been testing some things out.

I've regenerated the 365-day files now, and both the minified and non-minified files have data:

I'll keep this issue open and double check it works as expected on the next automated run, this Friday. There should be enough quota by then :)

Hugo van Kemenade · Answer 2 · Sat Apr 20 2019 00:05:39 GMT+0800 (China Standard Time)

Today the 30-day file updated, but it was out of data for the 365-day file (f511df0). I've reset the 365 back to Wednesday (424f724) and updated the script not to deploy if there's quota error in future (cb66cbd). Will check again next Friday!

Boris Verkhovskiy · Answer 3 · Thu May 02 2019 21:14:13 GMT+0800 (China Standard Time)

@hugovk still empty.

FYI, when I open https://bigquery.cloud.google.com/dataset/the-psf:pypi it says "Unable to find dataset: the-psf:pyp"

Hugo van Kemenade · Answer 4 · Thu May 02 2019 21:39:54 GMT+0800 (China Standard Time)

Thanks for the info, I've updated the data files.

When I open https://bigquery.cloud.google.com/dataset/the-psf:pypi I see this:

Hugo van Kemenade · Answer 5 · Sat May 25 2019 00:40:59 GMT+0800 (China Standard Time)

The files have been generated fine for the past few weeks, I'll close this now. Thanks again!