[00:09:42] <MirahezeRelay>	 <charlicak35_, replying to pixldev> [1595fcff86b0b9339cce91bd] 2026-01-30 00:09:31: Fatal exception of type "MediaWiki\Storage\NameTableAccessException"
[00:27:59] <MirahezeRelay>	 <posix_memalign, replying to charlicak35_> [1/2] `Failed to access name from slot_roles using id = 1`
[00:28:00] <MirahezeRelay>	 <posix_memalign, replying to charlicak35_> [2/2] I think I know how to fix this
[00:28:40] <MirahezeRelay>	 <charlicak35_> is it a miraheze thing or did i fuck something up lol
[00:29:10] <MirahezeRelay>	 <posix_memalign> Should be fixed now
[00:29:40] <MirahezeRelay>	 <charlicak35_> works, thanks!
[00:29:42] <MirahezeRelay>	 <abaddriverlol, replying to charlicak35_> It happens sometimes when resetting a wiki
[00:29:43] <MirahezeRelay>	 <posix_memalign, replying to charlicak35_> [1/2] It's a known issue that happens a lot after a reset
[00:29:44] <MirahezeRelay>	 <posix_memalign, replying to charlicak35_> [2/2] https://meta.miraheze.org/wiki/Tech:Fixing_slot_roles_and_content_models
[00:29:48] <MirahezeRelay>	 <charlicak35_> ah
[00:30:02] <MirahezeRelay>	 <abaddriverlol> (maybe we should create a task and investigate this at some point)
[00:30:07] <MirahezeRelay>	 <abaddriverlol> it can't be impossible to fix
[10:09:07] <Frisk>	 https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Scribunto/+/1228547 Just wondering, what is the usual position of Miraheze when it comes to enabling settings like this one? Does the tech team have to discuss it in some place, it becomes an option in ManageWiki or something else?
[10:14:00] <MirahezeRelay>	 <abaddriverlol> I wrote this patch, but I think it would be difficult to enable it on all wikis as it might break modules under certain circumstances, and we can't realistically check all of them
[10:15:07] <MirahezeRelay>	 <abaddriverlol> We can add it to ManageWiki, the question is just whether the average wiki admin understands what it's doing and doesn't complain if the modules they imported from wikipedia or somewhere else don't work properly
[10:16:00] <Frisk>	 ahhh, thank you for your work! Makes sense. Welp, guess worst scenario is PR to mw-config to enable it for a wiki 🫠
[10:17:09] <MirahezeRelay>	 <abaddriverlol> yep
[10:17:39] <Frisk>	 I'll keep that in mind for the future, thank you for answer! Have a great day :)
[10:18:32] <MirahezeRelay>	 <abaddriverlol> no problem, you too!
[10:18:58] <Frisk>	 Thanks!
[14:20:40] <MirahezeRelay>	 <georgesmith8733_94508> Just won $2,500 on KAIWIN.CC with promo code: GIFT 💰💸 @everyone
[15:05:31] <MirahezeRelay>	 <whostacking> https://issue-tracker.miraheze.org/T14871
[15:06:14] <MirahezeRelay>	 <pskyechology> they're not going to get done any faster just because you're linking them here
[15:06:32] <MirahezeRelay>	 <whostacking> when i dont see any tags on tasks i typically link them here
[15:06:39] <MirahezeRelay>	 <whostacking> i just found out theres a workboard for resets
[15:06:44] <MirahezeRelay>	 <whostacking> so im doing that
[18:05:54] <MirahezeRelay>	 <coca.codes> [1/2] trying to log in
[18:05:55] <MirahezeRelay>	 <coca.codes> [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1466856970228207705/image.png?ex=697e4482&is=697cf302&hm=1d95be8a81a6c172bea81a90fe8327a207cf7cac0d8f30da56010796ee80ea74&
[18:06:15] <MirahezeRelay>	 <coca.codes> seems it works fine on the miraheze domain for some reason
[18:07:11] <MirahezeRelay>	 <pskyechology> @cosmicalpha loading CSS fails on auth.miraheze.org due to violating CSP for custom domains
[18:07:19] <MirahezeRelay>	 <cosmicalpha> Of course.
[18:11:51] <MirahezeRelay>	 <notaracham, replying to coca.codes> See #announcements , we are in the process of upgrading our login system.
[18:11:58] <MirahezeRelay>	 <coca.codes> yep yep
[18:12:04] <MirahezeRelay>	 <coca.codes> thanks for your work :)
[18:12:35] <MirahezeRelay>	 <notaracham> Ope, I spoke too soon, this may actually be a tech issue as the deployment should be finished
[18:13:01] <MirahezeRelay>	 <pixldev, replying to notaracham> Deployment is finished
[18:13:15] <MirahezeRelay>	 <pixldev> Currently working on a few issues popping up on login and CSS for CDs
[18:13:46] <MirahezeRelay>	 <notaracham> Thanks Pix, can confirm I see the same CSS issue but was able to log in to a wiki with a custom domain
[18:14:32] <MirahezeRelay>	 <pixldev> I’ll test on the bus
[18:14:44] <MirahezeRelay>	 <pixldev> aka when I’m not procrastinating in math class because I entirely forgot adhd meds today
[18:24:55] <MirahezeRelay>	 <rhinosf1> @cosmicalpha some wikis throwing permission errors seems to be reproducible too
[18:25:15] <MirahezeRelay>	 <rhinosf1> I can reproduce on https://overkill.miraheze.org/Special:ManageWiki from a none staff account
[18:44:25] <MirahezeRelay>	 <ykm.matthew> i’m having issues logging on
[18:59:01] <MirahezeRelay>	 <pskyechology> still seeing CSP errors despite chucking on no caching refreshes and debug mode
[18:59:28] <MirahezeRelay>	 <pskyechology> [1/2] <https://tagging.wiki>
[18:59:28] <MirahezeRelay>	 <pskyechology> [2/2] <https://fischipedia.org/wiki/Fisch_Wiki>
[19:14:18] <MirahezeRelay>	 <cosmicalpha, replying to pskyechology> I wonder if cache somehow as I can confirm some custom domains work. Ones I originally tested did.
[19:15:02] <MirahezeRelay>	 <pskyechology> its not hitting cf or varnish
[19:18:07] <MirahezeRelay>	 <cosmicalpha, replying to pskyechology> Oh... I think I may know what is causing this...
[19:18:26] <MirahezeRelay>	 <cosmicalpha> Hard redirect on the miraheze.org domain so even manually forcing it isnt working.
[19:18:46] <MirahezeRelay>	 <pskyechology> aha
[20:05:59] <MirahezeRelay>	 <.labster> Still no styling when trying to login from allthetropes.org
[20:06:43] <MirahezeRelay>	 <cosmicalpha, replying to .labster> Aware. Happens when we force redirect the miraheze.org domain. Im working on it.
[20:08:32] <MirahezeRelay>	 <.labster> That said, login persisting across domains is working better than previously
[20:09:36] <MirahezeRelay>	 <notaracham> Haven't been logged out once despite hopping multiple custom domains/new attaches to my wobbly account, so a happy improvement
[20:10:40] <MirahezeRelay>	 <pixldev> I presume it would be safe to switch MFA to WebAuthn now?
[20:12:31] <MirahezeRelay>	 <cosmicalpha, replying to pixldev> It should be. Let me know if you have any issues.
[20:13:16] <MirahezeRelay>	 <pixldev, replying to cosmicalpha> Will move over soon
[20:14:33] <MirahezeRelay>	 <pixldev> pix about to be a very happy wiki man
[20:14:47] <MirahezeRelay>	 <pixldev> after he gets a sweater on
[20:15:43] <MirahezeRelay>	 <.labster, replying to abaddriverlol> Great patch, that one config setting would essentially remove the use cases for Extension:Variables in some deployments that I've seen
[21:39:25] <MirahezeRelay>	 <pskyechology> @cosmicalpha can confirm as working now
[21:39:33] <MirahezeRelay>	 <cosmicalpha> Great thanks!
[22:57:22] <MirahezeRelay>	 <croomfolk> [1/2] Hi, sorry for what may be an offtopic question. My browser sanitiser rejects a custom font I uploaded to a wiki. To my understanding that's an issue between the woff2 file and the browser, not Miraheze-specific. I have seen this webfont in use on other websites so I know it's possible to get it working, but cannot find information on repairing/remaking woff2s. Would someone have gu
[22:57:22] <MirahezeRelay>	 <croomfolk> [2/2] idance on this?
[22:58:12] <MirahezeRelay>	 <croomfolk> The error messages are ⁨`Bad cmap subtable`⁩, ⁨`Failed to parse table`⁩, then ⁨`rejected by sanitizer`⁩