well thing is if you don't change anythign it won't change. stale accounts (those in which nothing was updated since the last update) don't get updated via the cronjob.
Der Idiot wrote:well thing is if you don't change anythign it won't change. stale accounts (those in which nothing was updated since the last update) don't get updated via the cronjob.
Considered that, but discounted by adding &do=latest and noting that there have been mylist additions well within the boundary.
I think epoxi is on the money, will just have to pamper him till he fixes up the cron.
The user was correctly marked with statsstale when I checked just now. After running the user stats cron job manually all the counters seem to be ok again too.
The issue seems to arrise only when users modify their mylist the first time within 24h exactly while the user stats cron job is running.
The problem there is that the user stats cron job does not store the list of users with statsstale set to true locally. But instead directly uses it in db queries at different points in time.
This means that if the user was not marked statsstale at the beginning, none of that users db entries will be counted. If the user is then marked with statsstale before the results are written back to the db, the user's stats are overwritten with zeros.