[06:08:37] hmmmmmmm https://www.mediawiki.org/wiki/Extension:Patroller [06:08:46] latest update 2017 you say [06:09:59] @abaddriverlol whats the easiest way to check if an extension won't just go boom because of changes to core or smt (If i recall correctly we had/are having a lot of dropped classnames soon or something?) [06:12:05] i dont think you need to check for something last updated in 2017 [06:38:35] there’s been bump commits recently, i dont wanna dig to see if its had minor fixes to keep it working that no one put on mw.orh [07:09:48] The "latest version" thing is inaccurate because it needs to be manually updated. [07:09:59] [1/2] https://github.com/wikimedia/mediawiki-extensions-Patroller/commit/5ccee8a5673a13bcd6036d50b05aa38ea8726d8d [07:10:00] [2/2] There's a fix from 3 weeks ago. [07:10:19] Without it the extension would be incompatible with 1.44. [21:42:25] @originalauthority I wonder if we can revert this change, so the deletion page is sent to the client in `MW_FINAL_SETUP_CALLBACK`, then let the process continue until BeforeInitialize/ApiBeforeMain, where we sync the CreateWiki/ManageWiki caches, and then kill the process [21:42:44] This should fix any user-facing performance impact the change had [21:43:17] Because the deletion page is sent with a Content-length header anyway [21:46:16] Maybe [21:46:42] What performance change does it have? Theoretically it should be no worse than normal viewing of a wiki? [21:49:54] yeah, but it would be faster than that lol [21:50:16] practically that's probably irrelevant, but improving performance can't harm [22:04:05] I guess yeah maybe try it - I think my reason for doing it that way myself was that I was accessing MediaWiki services to generate dumps and provide the link, prolly don't need that for Miraheze implementation so