-
Notifications
You must be signed in to change notification settings - Fork 644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package statistics don't appear to be updating (again). #2503
Comments
Thanks for reporting this we are aware of the issue. We are currently prioritizing other site stability issues over the stats, but we plan to get these up to date again as soon as possible. |
@johnataylor May I know the frequency of the package’s download count update? |
I am confused .. the statistic was working again as late as beginning of last week .. somewhere after 16-18 july it was failing again. How can this keep happening? |
FWIW my stats are still stuck on Apr 22. Patiently waiting but would be nice to see a resolution... |
Same here: "Statistics last updated at 2015-04-22 21:15:57 UTC." https://www.nuget.org/stats/packages/FileHelpers?groupby=Version The new versions stats are not there, just the 6 weeks before Apr 22 |
Working on it, @xavierdecoster is typing like a madman to get this out :-) |
👍 |
Woohoo. Seems like we have stats again. Will monitor and see if they roll the update. |
@9swampy should be good now :-) |
We are working on data point roll-ups to avoid capacity problems. Jobs are a little behind but updates should soon be visible. |
@geoffreymcgill Just noticed it got updated |
It looks stuck again? |
We are working on data roll-ups. Statistics updates on the web site may experience delays as we occasionally have to disable the background jobs during the roll-up process. |
Any idea when its all is up to date? Can this get posted on status.nuget.org? |
Seems to be stalled again :-( |
Reopening #2380, #2329 & #2278, perhaps unrelated but same issue - none of my package statistics have been updated since 2015-04-22, interestingly a couple of days after all the above issues were "fixed and closed".
The text was updated successfully, but these errors were encountered: