Category talk:Non-free files with orphaned versions more than 7 days old

@BU Rob13, Stefan2, and Train2104: Here's an odd one. This category is virtually empty (9 files at writing). If I use AWB in pre-parse mode or Category:Non-free files with orphaned versions and skip all the files with a date 6 days old or less, I am left with 7355 files which are over 7 days old. To me, it seems that the queue system (Help:Job queue which moves files that change cats, but without an edit due to a date change), is not precessing the files - some go well back File:Жорстоке небо - Cruel Sky (cover).jpg - should have been processed on the 13th. I can't see any way of doing anything that will improve it (save doing 7355 null edits - I'm sure that won't go down well...) Anyone know a mechanism of fixing the problem, or know someone who can? Is it anything (I would have thought unlikely) to do with the change of date type in the template ( or Train2104's edit of the 6th - when it seems to have slowed - co-incidence?). Ronhjones ^(Talk) 20:07, 19 July 2017 (UTC)[reply]

@Ronhjones: Actually, we always do null edits. Mediawiki's time parser functions suck; they don't update automatically. I think Joes Null Bot does it? Maybe it's down. Out of town currently so I'll be able to do more tomorrow. ~ Rob₁₃^Talk 20:56, 19 July 2017 (UTC)[reply]

@BU Rob13: Cheers Rob, you are correct - it's User:Joe's Null Bot task 8, as they are null edits, there is no user contribution to check - I'll ping the bot owner - @Joe Decker:. Ronhjones ^(Talk) 21:43, 19 July 2017 (UTC)[reply]

I'm on it. There's some sanity checks in the null bot code for how large this category is expected to be, and task 8 hit one. It was limiting itself to 2000/day. I'll push through a complete run immediately. (It will still take a couple/few hours to run.) Thanks for the ping! --joe decker ^talk 22:31, 19 July 2017 (UTC) @Ronhjones:, @BU Rob13:.[reply]

@Joe Decker: Sorry Joe, obviously you have missed out on the discussions regarding user:RonBot. Now we can process these files automatically, I have raised the tagging rate of adding {{non-free reduce}} - I think I had a spare day to kill and went over your limit! (although DatBot 6 sometimes takes a while to catch up and then does a whole load). I'll remember not to do that again. Ronhjones ^(Talk) 23:52, 19 July 2017 (UTC)[reply]

Just realised - if it's doing the whole cat of Category:Non-free files with orphaned versions, then that is seven days of tagging, and could well be 7000 files or more. Ronhjones ^(Talk) 00:28, 20 July 2017 (UTC)[reply]

No big deal to change the limit, it's mostly there so that when things change drastically, I get kicked to figure out whether it's because something has changed or because there's an unexpected problem. I'll up the default limit too. --joe decker ^talk 05:46, 20 July 2017 (UTC)[reply]

PS: I'm currently showing that category as having around thirteen thousand entries. --joe decker ^talk 05:53, 20 July 2017 (UTC)[reply]

@Joe Decker: Thanks for upping the limit. I did say I'd been busy, obviously busier than I thought! There are still 168,000 files greater than the WP:Image resolution guideline (of which 30,000 are so close they would not be reduced) and I'm getting a rejection rate to the reduction request (either by myself when viewing the image, or by someone else after I have added a tag) of about 0.2% - so there are (potentially) a lot more files to do. I would expect this to go on for many, many months. Once we have the bulk of the files down at the guideline, then the rate will just drop to the new and updated files (50 a day typically). Ronhjones ^(Talk) 11:24, 20 July 2017 (UTC)[reply]

@Ronhjones: Understood, and it's valuable work that's doing. Turns out I'll need to do a bit of coding to get past 5000, I'll try and to that by the weekend. (There's a limit in the API I'm using.) --joe decker ^talk 13:47, 20 July 2017 (UTC)[reply]