WDQ appears to be really behind again. http://wdq.wmflabs.org/stats currently says just after 1am on the 17th (and last night, it said around 5am on the 17th, so it seems to have gone backwards somehow).
Topic on User talk:Magnus Manske
THe SPARQL query system has the same issue. Apparently, SuccuBot flooded Recent Changes, so now both are struggling to keep up. Should reslove itself soon-ish.
Yeah, I saw that mentioned after commenting here. It looks like it's updating but slower than real time, is it likely to continue at the same rate until it makes it through all of SuccuBot's edits?
That would be my interpretation.
SPARQL is up-to-date again.
WDQ is now at 2015-11-18T03:27:53Z
I hope it will catch up.
So do I.
It's now showing 2015-11-16T22:37:05Z for me which is over a day earlier o_O Any idea why it keeps jumping backwards?
Tardis?
When it crashes, it reverts to the last saved state. Last dump is from the 16th, so nothing can be done but wait a week.
Ah.. no luck. I was wondering why Listeria failed .. no values back then.
Maybe we should ask for an intermediary dump. At least, this makes me use more of SPARQL.
Been watching the stats all weekend and it keeps bouncing back and forth between the 17th and the 16th :-(
Anything that can be done to get it going again? --VicVal (talk) 18:33, 23 November 2015 (UTC)
I tried to import today's dump, but the import fails after half an hour or so, reason unknown. Debugging could take days, if I had nothing else to do.
I'll just continue to add data then - and verify ones we are back again :-) --VicVal (talk) 21:33, 23 November 2015 (UTC)
It's about the same date since queries like https://tools.wmflabs.org/wikidata-todo/beacon.php?prop=214&source=227&site= are grossly truncated by timeout error messages.
It's fixed now, ~1 day behind, catching up.
Thanks for fixing it. It's a bit risky to do a series of edits without it being available to check them if needed.