[04:52:18] Why is wgDataMapsEnableFandomPortingTools in ManageWiki? https://github.com/wiki-gg-oss/mediawiki-extensions-DataMaps/issues/315 [04:54:37] [1/2] huh [04:54:37] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1423171289983750204/message.txt?ex=68df570c&is=68de058c&hm=17e0a7e33d601fed61dbe3e171a1ebd9c897543d3eb425cb9016e865f64d6012& [04:54:44] uh now [04:54:59] https://github.com/miraheze/mw-config/blob/eed4fee1737570af6796d12296426d6fac4c0ff5/GlobalSettings.php#L616 [08:11:06] [1/16] https://lists.wikimedia.org/hyperkitty/list/wikitech-l@lists.wikimedia.org/thread/RHDVZ3XIQ2NJR3GPXAN7RENYWOOIAFTU/'Security pre-release announcement: 1.39.14 / 1.43.4 / 1.44.1 [08:11:06] [2/16] Sam Reed @ 1 Oct 2025 10:33 p.m. [08:11:07] [3/16] Hi all, [08:11:07] [4/16] On Thursday we will be issuing a security and maintenance release to all supported branches of MediaWiki. [08:11:07] [5/16] The new releases will be: [08:11:08] [6/16] - 1.39.14 [08:11:08] [7/16] - 1.43.4 [08:11:08] [8/16] - 1.44.1 [08:11:08] [9/16] This will also resolve security issues in bundled extensions, along with bug fixes included for maintenance reasons. [08:11:09] [10/16] These security issues also affect many unsupported versions of MediaWiki. [08:11:09] [11/16] We will make the fixes available in the respective release branches and master in git. Tarballs will be available for the above mentioned point releases as well. [08:11:10] [12/16] A summary of some of the security fixes that have gone into non-bundled MediaWiki extensions will also follow later. [08:11:10] [13/16] As a reminder, MediaWiki 1.35 became end of life (EOL) in December 2023, MediaWiki 1.40 became EOL in June 2024, MediaWiki 1.41 became EOL in December 2024 and MediaWiki 1.42 became EOL at the end of June 2025. [08:11:11] [14/16] MediaWiki 1.39 (the old LTS before 1.43) becomes EOL in December 2025. It is strongly recommended to upgrade to 1.43 (the next LTS after 1.39), which will be supported until December 2027. [08:11:11] [15/16] More information on these timelines can be viewed on the Version lifecycle page at [1]. [08:11:12] [16/16] [1] https://www.mediawiki.org/wiki/Version_lifecycle [11:05:35] Nvm its becoming slow again [11:22:49] Also it keeps saying the server did not respond in the expected time when i try to save changes [13:54:14] where are you based (i just need the region) [13:54:25] since performance should have improved (at least it has for me) [13:54:51] we increased the php-opcache and apcu cache and we also switched from cloudflare smart cache (which was causing performance degradation) [14:05:54] Well increasing apcu likely did nothing since Miraheze only uses it for LanguageConverter which all wikis don't have enabled so that was probably a waste of time [14:06:15] Oh that's a MediaWiki thing? [14:07:06] Still probably less effective than allocating whatever was allocated to APCu to Op [14:07:47] nah, apcu was being fully used [14:07:53] By what? [14:08:06] It's not used by anything in mw-config [14:08:11] Except LanguageConverter [14:08:14] i'm not sure exactly, but we have a graph with metrics for opcache/apcu [14:08:24] which led me to increasing it [14:08:37] see https://grafana.wikitide.net/d/GtxbP1Xnk/mediawiki?orgId=1&from=now-1h&to=now&timezone=browser&var-node=mw151&var-job=$__all (bottom) [14:09:50] opcache may needsto be increased further (since we do php cache files). [14:10:23] but iirc this has had a impact on jobs (latency is lower since i increased) [14:10:58] i want to add https://github.com/wikimedia/operations-puppet/blob/a074f13510cb10f5851683dc40e028ff540fd2c4/modules/profile/manifests/mediawiki/php/restarts.pp#L69 as well [14:11:30] but that'll require us to build either a small http service to send requests for that MW server to depool then repool itsself. [14:11:33] or use varnishadm [14:11:57] (i'm kinda leaning towards the former). [14:13:28] It would be good to see what's actually inside APCu since 294k keys sounds excessive if only language converter is using it (maybe something else is but mw-config doesn't indicate so) [14:39:21] @originalauthority seems it's used with the resource loader [14:42:55] also used in file contents hasher [16:40:37] https://discord.com/channels/407504499280707585/407537962553966603/1423348451852292230 a ton of echo events for declined wiki request notifications use an incorrect key for the comment, this is the third report of this error already [16:41:34] I fixed it manually with https://discord.com/channels/407504499280707585/808001911868489748/1422198345597845526 for a user a few days ago but it would be good to know why this was changed and why the key wasn't migrated before I run more SQL updates [16:41:49] or actually maybe we should fix it in createwiki [16:48:44] if anybody is available to review [17:12:18] done [17:12:31] thx [18:45:35] europe [18:46:08] do you have a link to the wiki you use? [18:46:17] it all seems to load relatively quick for me [18:46:19] yh but its private [18:46:24] that's ok [18:46:39] https://nicholasworld.miraheze.org/wiki/Main_Page [18:47:00] loaded quickly for me [18:47:07] (i'm based in europe as well, UK) [18:47:27] sometimes when i clear the cache it works until i make some edits then it takes a while to edit and then its slow [18:48:08] i tried to edit which is fast, does it work for you now? [18:53:13] could it be just your network ? [18:55:37] yh idk what the problem was tbh [18:55:48] could be but everything else is fast js fine [18:56:04] when you said it was slow, did you try it out then? [18:56:15] because we've changed some things in the last 2 weeks [18:56:34] i guess maybe 3 weeks [19:49:10] when [19:51:42] When you wrote in here that it was slow [20:34:29] Yes [20:35:10] It's still slow now for me so maybe it is just my connection especially because my other wiki is also slow but it works fine on other websites and apparently my internet speed is fast [22:52:58] Do we still have the Replace Text restrictions on wikis created prior to May 11 2024? [22:53:00] https://meta.miraheze.org/wiki/Steward_requests/Restricted_changes#Baubles_Wiki [22:54:00] Yes, as long as there as still compressed revisions in the DB (there's a script to check that) ReplaceText can't be enabled [22:54:20] Could you run on this one? [22:54:24] Created Feb 2024 [22:56:49] https://cdn.discordapp.com/attachments/1006789349498699827/1423443635457888397/message.txt?ex=68e054b0&is=68df0330&hm=2a8120b389982443b9e202e1c1caa2ccfa2391e722d11fd9233c00a29c52dd60& [23:01:29] Can they be uncompressed? [23:02:53] That requires editing each of those pages [23:03:12] And null edits don't work according to