[Wikidata-bugs] [Maniphest] [Commented On] T240370: Maxlag=5 for Petscan

2019-12-11 Thread Pintoch
Pintoch added a comment. Thanks for the analysis! Whether this is a breaking change or not is not my concern: Petscan and other mass-editing tools based on Widar should play by the book. I can provide a simple patch which ensures maxlag=5 is applied to all Widar edits: if someone wants to

[Wikidata-bugs] [Maniphest] [Commented On] T240370: Maxlag=5 for Petscan

2019-12-11 Thread Bugreporter
Bugreporter added a comment. PetScan do edits via Widar: https://github.com/magnusmanske/petscan_rs/blob/master/html/autolist.js Widar itself does not use maxlag at all as of 2015:

[Wikidata-bugs] [Maniphest] [Commented On] T240370: Maxlag=5 for Petscan

2019-12-11 Thread Pintoch
Pintoch added a comment. @Bugreporter have you got details of where this behaviour is currently implemented in PetScan? In particular, how do you request the current maxlag with the MediaWiki API? TASK DETAIL https://phabricator.wikimedia.org/T240370 EMAIL PREFERENCES

[Wikidata-bugs] [Maniphest] [Commented On] T240370: Maxlag=5 for Petscan

2019-12-10 Thread Pintoch
Pintoch added a comment. I've had a quick look at the code to see if I could submit a patch for this myself but it is not clear to me where the edits are done - I have looked in petscan_rs and wikibase_rs to no avail. Petscan edits might be done in the browser by sending them to some