[00:15:59] @cosmicalpha i've opened https://github.com/miraheze/mw-config/pull/6653 [00:16:09] it's on the v [00:16:53] Thank you, I am about to go to dinner, I can merge and update announcements when I return if you want? [00:17:08] yup, only if the script finished tho [00:17:19] Yeah. Will do. [00:17:35] i'm unable to use the maths that rhinos used to estimate the time it would complete tho (not good at that stuff lol) [00:17:35] Maybe be a little late if it finishes while I'm gone though but that should be fine. [00:18:04] it's on w now [00:18:08] Also, is set global read_only enabled also do I need to turn that off as well? [00:18:15] oh [00:18:52] it's off i think (it's set at 0) [00:19:14] oh, okay thanks [00:19:53] If it is finished before you go, feel free to take RO out and post in #announcements (no ping IMO) it not I can when I return. [00:32:05] it's on z [00:38:43] whenever you remove RO, I'll undo my disabling of renames/vanishes [00:39:22] it's finished [00:40:31] taking out of read only [00:40:44] ppushed my commit [00:42:58] https://meta.miraheze.org/wiki/Special:GlobalRenameProgress [00:43:10] seeming like these 5 renames may need to be kicked [00:48:02] yes please [01:00:39] all are now done [01:01:53] @paladox could you press the publish button on the announcement so it can be seen in other servers? [01:01:55] for slightly more visibility, and if it haven't already been done (i don't see this in my server) [01:02:07] lmeow [01:02:18] damn, at the same time too [01:02:36] Done [01:03:09] I wonder how many servers have subscribed to miraheze, guess only server admins can find out [01:32:15] Thanks @paladox [04:46:24] Morning [04:46:27] And thank you [04:46:37] Disk space dropped 20.9% [04:47:04] Which is ~205G saved [04:47:10] Which is slightly insane [04:47:53] CPU & disk look a little high on db161 but cache is still warming up so that's not a surprise [04:48:11] Jobs reached a high of over half a million but is clearing well too [04:49:26] @cosmicalpha is it worth trying optimise on db192? [04:49:40] Given it regularly seems full [04:50:17] That's the only one that's actually a concern for disk space [07:38:37] [1/2] https://meta.miraheze.org/wiki/Miraheze_Meta?action=history [07:38:38] [2/2] For some reason, an import from a different page has been mixed in, which prevents me from editing the page. Therefore, I need to delete it once, exclude those imported versions, and restore it. However, because it has a large history and is a translation target page, I'm not sure how I should proceed [07:42:44] [1/2] it's been imported and revisions like https://meta.miraheze.org/wiki/Miraheze_Meta?diff=prev&oldid=473373 are throwing a [07:42:44] [2/2] [3ad0fce620e65f98a3d36cb8] 2026-11-16 07:42:15: Fatal exception of type "MediaWiki\Revision\RevisionAccessException" like other old revs have before iirc [14:48:21] https://issue-tracker.miraheze.org/T16534#330703 any idea on this? we may need `conflicts` for `ManageWikiSettings.php` [14:52:57] looks like phorge upstream have figured out the github login issue, and a fix is on the way (not yet landed) [14:54:55] and when the conflicted ext is enabled the setting also needs to be cleared. sounds like a bit complicated and i'm not sure if there's other usage than the wikibase/unlinkedwikibase one [17:09:35] …the fix is now landed and the ticket closed, we just have to update our install to get the fix