[00:23:14] I am sorry if I thrashed the job queue [00:28:15] I keep getting `503 Service Unavailable. No server is available to handle this request.` when using Special:Search on my wiki. Is this a known issue? [00:28:41] Mainly when trying to search for `Special:ManageWiki/extensions` in the search box [00:29:05] I am getting it too [00:29:16] thanks :) [00:42:41] There are more than 600 wikis so I'd probably not do that. The only trace of usage is probably in the logs. I assume imports are logged but exports are not, which makes this even harder. [00:52:40] I guess you can run some SQL to check the logs. If you figure out a foreachwikindblist call that works on test151 I can run it in prod for you. [01:02:27] We are aware of service degredation (hence the tons of alerts in -tech-ops), we have opened a ticket with Fiberstate to get it sorted [01:17:44] Thanks, @MacFan4000. Is it worth Discord mods doing a minor announcement for this? [01:57:04] [1/2] I'm also affected by the downtime and would just like to know a ETA of when it will be back up [01:57:04] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1538728337705275443/image.png?ex=6a83bbef&is=6a826a6f&hm=37080ed65e5a5f41df9d12bcb0aa07e9a134711f6375c942068ef629b910cee5& [01:59:59] [1/2] Phorge is giving me a 503 when searching, and also errored when trying to see [[phorge:T18760]]. [01:59:59] [2/2] I also can’t seem to add any comments on the task regarding the mwtask161 outage nor it shows a preview. [02:00:00]

[02:04:03] That was related to the db161 outage, It’s currently being depooled. [02:09:43] thanks for the update [02:14:59] doubt those are related, I have no idea what's up with those 503s [12:08:23] The phorge bugs seem to be fixed now [13:00:19] It is not [13:01:49] [1/2] I am wondering if I was too specific https://issue-tracker.miraheze.org/T15801 ? [13:01:49] [2/2] File uploads are still credited to the wrong users. [13:02:23] Very thankful for all help, I am sorry for all questions and stuff. [13:08:33] It may be a bug in our script [13:08:52] Phorge is currently unavailable while we debug the 503s last night [13:09:33] Weird, I wasn’t getting those 503s while doing a search at the time of writing that unlike last night [13:09:47] It was half fixed and left a mess last night [13:09:59] We're going to rollback last nights fix and try to fix it for real [13:17:37] [1/2] Edit histories changed, file uploads didn't. 🙂 [13:17:37] [2/2] Should I do something more with the ticket, or is this enough for when phorge is up again? [13:17:48] It should be enough [13:21:04] Cool! Could you ping me when upload credits are fixed? 🙂 [13:21:15] You'll get a reply on the task [13:21:22] I doubt it will be before Phorge is back [13:34:19] [1/3] For those on Libera [13:34:19] [2/3] Phorge is currently read only while we investigate issues in further detail that were reported last night. [13:34:19] [3/3] The next update is expected in around 2 hours time. [14:58:00] Yeah some tickets are broken whilst some work how bizzare [14:58:19] It's a glitch in the matrix!!! [15:07:05] Or phorge [15:15:37] The update is that there is no update [15:57:14] I think phorge is fixed [15:58:51] fyi @originalauthority @karpeth @randomizer.jpeg [15:59:45] oh, just got 2 random e-mails for commits I made months ago [15:59:55] or well, more than a year ago [15:59:58] wow [15:59:59] uhhh, thanks Phorge? [16:00:33] Frisk: was it the SSL repo? [16:00:56] yes [16:01:00] both were [16:01:12] Frisk: that is known [16:01:23] cool cool then [16:01:25] Phorge had managed to corrupt its copy of the git repos on disk [16:01:31] so I had to rebuild it [16:01:36] holy SSL [16:01:38] good job Phorge [16:02:03] all of the repos were affected [16:02:10] but we stopped syncing SSL to phorge [16:02:22] so it now thinks that months of changes were made immediately [16:03:03] yup [16:03:22] ill just use https://issue-tracker.miraheze.org/feed/query/ofGNfSPhc_m0/#R for now [16:05:21] GitHub is chewing rocks rightn ow. [16:06:14] Damn, this almost every service is down. [16:06:49] i had to use the CLI [16:06:52] github web is down [16:06:52] what projects should https://issue-tracker.miraheze.org/T15858 have [16:06:58] yup lol [16:07:19] Do I still need to add manual redirects for miraheze to custom domains? [16:07:25] updated the tag [16:07:26] no [16:07:35] we auto roll redirects [16:07:37] Not sure if it's because of GitHub dying, but my custom domain redirects to the mira subdomain instead of the other way around. [16:07:41] https://doorsgame.wiki/ [16:07:54] thought it was SSL [16:08:13] how much traffic did doors get on fandom [16:08:15] and closed it [16:08:25] Uhhhh, million page views a month? [16:08:31] interesting [16:08:32] weird [16:08:36] wish you the best of luck with the move [16:08:37] but it shouldn't be [16:08:51] I've heard from a lot of folks that the google jail problem is nasty these days [16:08:52] has it been more than a day since your CD was added [16:08:58] I just bought the domain, is there anything specific on CF that's contributing to it? [16:09:03] Yes. [16:09:07] so hopefully the custom domain won't cause problems for y'all [16:09:15] it should have a redirect then [16:09:27] from mh -> cd [16:09:41] have you been/will you be shouting the migration from all applicable doors related rooftops [16:09:58] Yes. [16:10:20] I wanted the custom domain setup today so I could announce the custom domain first, but then it decided to do this,' [16:10:51] Well, as far as I was aware, the SSL bot added a redirect, but now I can't verify thawt. [16:12:54] yeah, seem that things can still be pushed via cli even if the web ui is broken [16:16:13] Check diffusion on Phorge [16:16:19] Given I just rebuilt it [16:16:33] Ah, so that's why I got that email. [16:16:34] It will have SSL up to about 15 minutes ago [16:16:37] About a PR I made in March. [16:16:41] Yes [16:16:55] We stopped syncing ssl but diffusion got corrupted [16:17:04] So I had to recreate the repos [16:18:14] The SSL configuration in diffusion? [16:20:11] Here it is: https://issue-tracker.miraheze.org/rSSL1e5e577893f1e870a325d7da637eff89cf90f252 [16:20:26] [1/8] ```yaml [16:20:26] [2/8] doorswiki_autoredirect: [16:20:26] [3/8] ca: Cloudflare [16:20:27] [4/8] first_seen: '2026-08-17T10:00:13.887581+00:00' [16:20:27] [5/8] redirect: doorsgame.wiki [16:20:27] [6/8] sslname: miraheze-origin-cert [16:20:28] [7/8] url: doors.miraheze.org [16:20:28] [8/8] ``` [17:01:14] GitHub seems to be back up now [19:42:55] anyone have the pink miraheze logo [19:44:30] found it [19:51:17] anyone know what the collation table is [19:51:26] getting an error on https://meta.mirabeta.org/wiki/Category:Global_policies [19:52:57] [1/2] For future reference: [19:52:57] [2/2] https://commons.miraheze.org/wiki/Category:Miraheze_Logos [20:02:13] Not much, but [20:03:27] hm, think the db error is from a missing sql patch [20:07:30] The whole table not existing seems like a bit more than just a missing sql patch [20:10:03] Maybe something tied to the translate extension? Seems like it's got a stray translate tag in the categories section of the page... [20:10:25] huh [20:10:45] https://cdn.discordapp.com/attachments/1006789349498699827/1539003572908458125/image.png?ex=6a84bc45&is=6a836ac5&hm=a9c81da09d98656e347c206eba730fe30c466e35f6b33d4227c8bcd35d176cbc& [20:11:11] Not familiar with that particular usage though [20:11:34] Oh, to put different lang versions of types of pages in a category [20:11:51] so Category:Global policies/pt is in Category:Policies/pt [20:13:45] looking into how Data Transfer works, doubt there's any real way (other than checking how many times a URL has been hit per wiki, ew) of tracing usage of it for exports [20:13:54] Imports also not sure if they have their own log [20:14:22] just logged as creating a page [20:14:40] so unless we query for all page edits by the default edit summary.. [20:15:42] this is new I think, I don't believe prod currently makes local log entries for remove right changes https://exttest.mirabeta.org/wiki/Special:Log?logid=3128 [20:26:26] @rhinosf1 if you're planning on taking https://issue-tracker.miraheze.org/T15771 do you want me to assign you to the task (blitzing through some phorge clerking rn) [20:29:33] https://issue-tracker.miraheze.org/T15697 needs to get a move on, as it seems to have a little more than a week before the AI reviewer drives off a cliff [20:38:55] Oh I promised that didn't I [20:38:59] Yes please do [20:39:07] Then I have it on a list [20:39:35] I will do that tomorrow [20:39:43] If I haven't done it by the time you wake up, spam me [20:41:09] luck for you, I sleep like a rock [20:41:14] so you got until [20:41:47] probably 2pm for you [20:44:33] assigned [21:33:01] Is the script readable somewhere; I would like to learn. 🙂 [21:33:37] I think it's a maint script in the magic repo [21:34:00] but yes, as much as can be open source, is [21:36:28] Is there a link? I am not fully familiar. 🙂 [21:43:08] I think it's https://github.com/miraheze/MirahezeMagic/blob/main/maintenance/AssignImportedEdits.php [21:43:52] [1/2] Thanks! [21:43:53] [2/2] Discovered another minor problem; what's the default font for mw-page-title-main ? [21:44:28] we have 0-s in some pagetitles rendered as lowercase o, which according to the knowledgeable on our wiki is a font problem. [21:44:41] and I'd like to make as few small changes as possible. [21:49:36] Looking at the script, I see that I would need to understand the underlying database. It looks straightforward, but I can see how uploaded files can be missed.