[00:12:48] [02mw-config] 07pixDeVl opened pull request 03#5649: T12526: Add redundent langs to DisabledLanguages on meta - 13https://github.com/miraheze/mw-config/pull/5649 [00:13:40] miraheze/mw-config - pixDeVl the build passed. [00:14:40] yaaaaay [00:17:30] @cosmicalpha why is de depooled, shame reason as ja and au? [00:30:07] @cosmicalpha [00:30:20] ill never understand the ping logic [00:31:38] you added an extra whitespace before the ping. A logic error in bot maybe idk for sure lol [00:31:59] I ADDED THE WHITESPACE **FOR** IT TO WORK [00:32:00] GAH [00:32:17] Yes same reason [00:32:20] because (@cosmicalpha) dont work [00:32:31] Try cosmicalpha: test [00:32:34] when its surrounded by smt [00:32:48] cosmicalpha: discord is silly [00:32:56] Thank you Discord, very cool! [00:33:16] brb opening an rfc to move to matrix [00:33:23] pixldev: hi? [00:33:35] oh works [00:33:42] magic [00:33:54] cosmic magic [00:33:58] ba dum tsi [00:34:07] @cosmicalpha test [00:34:16] I think at one point we did look into a Matrix bridge as well [00:34:25] but tbh, I don't think we'd have a big Matrix community [00:34:29] that worked lol [00:34:36] @cosmicalpha test [00:34:39] @ everyone [00:34:42] huh [00:34:43] :trollgod: [00:34:53] ooooo [00:34:58] it didn't relay that [00:35:17] It won't do anything it wrapps @ everyone and @ here in a code block [00:35:36] interesting [00:35:50] hmm [00:35:51] Also likely doesn’t have the ping everyone permission [00:36:12] It doesn't but measures so even if did it wont work [00:36:22] Why is the relay so lagged lol [00:36:23] You can still type @ everyone and have it not ping people if you don't have the proper perms [00:36:47] slow connection? [00:37:14] "8:35 AM <+ CosmicAlpha> It won't do anything it wrapps @ everyone and @ here in a code block" that message didn't even relay [00:37:16] oh nice, now if you don't want any messages relayed to Discord, you can just say @ everyone [00:37:28] @ everyone super secret IRC message [00:37:32] lol [00:37:39] @ everyone [00:37:47] I broke something in the bot I think [00:38:13] I think updating Discord.Net today may have broke something [00:38:30] I always wanted a no relay command but not @ everyone lol [00:40:23] Hmm did I forget to implement logging into the relay code lol it logs nothing at all [00:40:52] @ test [00:40:57] oh lol [00:41:02] @ I wonder [00:41:06] I w@nder [00:41:07] Yep [00:41:09] hmm [00:41:15] http://wm-bot.wmcloud.org/dump/%23miraheze-tech-ops.htm [00:41:15] @info [00:41:19] It only works if you have it in the beginning [00:41:42] @test [00:41:49] @ test [00:42:05] I'm tempted to @ everyone [00:42:24] It is a conflict between wm-bot and the relay code I think if a command in wm-bot exists it relays but otherwise not if starts with @ [00:42:39] oh nevermind lol [00:42:41] so odd [00:42:53] @ test breaks it [00:43:12] Super odd [00:44:20] Hmm thats not it either. Something to do with @ no idea beyond that [00:44:30] nice [00:44:37] now we can have @ secret messages [00:44:55] @ of course, if we disregard the fact that this channel is logged [00:45:25] It's an easter egg that even I who created the relay from scatch can be surprised by lol [00:45:52] I am tempted to not even try fixing as I almost like it lol [00:45:52] Literally just claire she’s the only person in the community i know (for sure) uses matrix [00:45:54] this reminds me of when Doug would use the interwiki feed as a sort of impromptu ad hoc conference room to send messages without being logged [00:46:16] What [00:46:20] why not [00:46:23] neglectable populace [00:46:39] just go to #supersecretbeeroom [00:47:14] you get ops in a new channel so you can fully control over invite [00:47:14] that works as well [00:47:36] my face contorted in response to that pfp [00:47:38] i love it [00:47:48] That is what PMs are for [00:48:00] In laughter* [00:48:07] nothing better than using a public channel [00:48:14] that's not very transited [00:48:14] lol [00:48:29] Hey I love how we all keep going back and forth between IRC & Discord [00:48:41] we need to give IRC some love [00:48:44] @ test [00:48:49] conference room implies 2 people [00:48:53] could be moee [00:48:54] doesn't happen tbat direction [00:48:59] could be 3 [00:49:13] could be gasp 4! [00:49:17] i can count [00:49:21] yeah, it'd be used to discuss matters with multiple users without it being relayed on #miraheze [00:50:53] Only reason I can see why you'd do that in a channel called interwiki feed is if you were having a conversation between yourselves and a couple of bots. If you want to do that use a whole new channel. I'm just confused lol [00:51:14] I'm not sure his reasoning for using the iw feed [00:51:20] or he'd sometimes use the meta feed [00:51:33] I’m not sure he knows the reasoning ngl [00:51:39] i don’t know doug well so [00:51:46] the venerable dough [00:52:16] dough? [00:52:24] Cocopuff would call him 'Dough' [00:52:33] I talk to some AI bots in my empty server sometimes. But I don't use a random IRC channel that makes no sense to use for that to have real conversations. [00:52:43] hey guys welcome back to the show on this episode we bake a former steward!!! [00:52:56] Steward pie [00:55:26] 🥧 [00:55:29] mmmmm [00:55:34] blueberry! [00:59:08] what flavor are steward [00:59:28] or any role [00:59:43] WC is apple i think [00:59:44] hmm [00:59:56] I was thinking of Steward as apple pie as well [01:00:04] im totally not just going off role color [01:01:57] Well, thinking of how a group would taste as a pie is interesting [01:02:21] i think GA would be rasberry maybe [01:03:08] agentisai: actually maybe make WC pumpkin and make stewards apple ye [01:42:25] [Grafana] FIRING: The mediawiki job queue has more than 2000 unclaimed jobs https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [01:43:16] there's two jobrunners [01:43:32] I would've hoped one of them was enough [01:45:48] hm? what i miss the logs are broken [01:46:51] job queue exploded [01:49:41] oh [01:49:58] average sunday explode, or, *tuesday* explode? [02:09:17] Higher job counts are normal at this point especially given that we have over 9k (non-deleted) wikis [02:11:23] If that's the case maybe we should adjust the threshold for the screaming [02:11:38] why am i 25 [02:11:45] im not that old [02:11:52] yaaay [02:12:24] also someone wanna merge https://github.com/miraheze/ManageWiki/pull/474 ? [02:13:06] It already was raised up from 500 [02:13:16] https://issue-tracker.miraheze.org/T12447 also has a PR ready i think [02:17:25] [Grafana] RESOLVED: High Job Queue Backlog https://grafana.wikitide.net/d/GtxbP1Xnk?orgId=1 [02:19:04] Looks like we still have 0 icinga alerts 🎉 [02:19:35] how long til that goes and why is it going to be a cp [02:20:20] There have been alerts on and off today, but they resolved themselves [02:21:23] mysterious network issue number 273? [02:59:42] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.21, 4.40, 1.92 [03:00:38] MacFan4000 I was wrong! It's opensearch, not cache [03:01:42] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 4.57, 4.39, 2.22 [03:30:29] [02ManageWiki] 07Universal-Omega closed pull request 03#474: T12340: Replace : in namespaces with _ - 13https://github.com/miraheze/ManageWiki/pull/474 [03:30:31] [02ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±2] 13https://github.com/miraheze/ManageWiki/compare/da2c38332d5f...668b4ceb51d9 [03:30:33] [02ManageWiki] 07BlankEclair 03668b4ce - T12340: Replace : in namespaces with _ (#474) [03:30:38] Merged [03:31:42] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.61, 6.59, 5.33 [03:32:23] gracias [03:32:31] No problem [03:32:50] ill ait for claire to confirm it worked before closing it [03:33:47] I guess I should upgrade ManageWiki then... [03:34:37] managewiki is in need of a few updates yeah [03:35:10] miraheze/ManageWiki - Universal-Omega the build has errored. [03:35:19] !log [universalomega@mwtask181] starting deploy of {'versions': '1.42', 'upgrade_extensions': 'ManageWiki'} to all [03:35:21] what now [03:35:24] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:35:32] !log [universalomega@mwtask181] finished deploy of {'versions': '1.42', 'upgrade_extensions': 'ManageWiki'} to all - SUCCESS in 14s [03:35:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:35:50] PixDeVl: ManageWiki updated [03:36:02] the build failed [03:36:22] Its fine. I need to go through a few of our extensions to fix CI [03:36:28] ah okay [03:36:31] what broke [03:36:48] I think it may be an upstream dependency we may be able to remove [03:37:16] Oh no that was a different extension [03:37:24] This was PHPCS issues only [03:38:36] [02ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ManageWiki/compare/668b4ceb51d9...3250108c7925 [03:38:37] [02ManageWiki] 07Universal-Omega 033250108 - Fix PHPCS [03:38:38] also can you grant metabetawiki crate `managewiki-permissions` right? since we never updated it since we split rights [03:39:09] and perms are fuuucked [03:39:23] [02ManageWiki] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ManageWiki/compare/3250108c7925...df2c8d8eea63 [03:39:24] [02ManageWiki] 07Universal-Omega 03df2c8d8 - Fix PHPCS [03:42:50] miraheze/ManageWiki - Universal-Omega the build has errored. [03:43:10] thank you miraheze-github [03:43:42] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 4.79, 6.18, 6.03 [03:44:38] miraheze/ManageWiki - Universal-Omega the build passed. [03:44:55] There we go! [03:45:03] !log [universalomega@mwtask181] starting deploy of {'versions': '1.42', 'upgrade_extensions': 'ManageWiki'} to all [03:45:09] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:45:16] !log [universalomega@mwtask181] finished deploy of {'versions': '1.42', 'upgrade_extensions': 'ManageWiki'} to all - SUCCESS in 13s [03:45:21] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [03:45:52] Not sure why I upgraded it when it just applies a few whitespaces but whatever lol [03:46:48] the PR itself? [03:47:06] already applied that [03:47:20] https://issue-tracker.miraheze.org/T12340 [03:47:22] a [03:48:02] also [03:48:03] [11:38:38 PM] also can you grant metabetawiki crate `managewiki-permissions` right? since we never updated it since we split rights [03:48:03] [11:39:09 PM] and perms are fuuucked [03:48:27] not sure if these were buried by botifico [04:08:29] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.22, 6.85, 6.54 [04:16:07] !log updated wiki.surf nameservers to cloudflare [04:16:12] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [04:21:46] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 5.32, 6.56, 6.70 [04:29:42] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.51, 6.83, 6.75 [04:30:03] [02mw-config] 07hurohukidaikon commented on pull request 03#5643: Update UploadWizard settings for kagagawiki - 13https://github.com/miraheze/mw-config/pull/5643#issuecomment-2323791998 [04:33:42] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 5.13, 6.35, 6.61 [05:09:01] PROBLEM - os162 Current Load on os162 is CRITICAL: LOAD CRITICAL - total load average: 8.05, 7.10, 6.57 [05:10:55] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.74, 7.31, 6.72 [05:14:42] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 6.13, 6.51, 6.52 [06:27:46] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.02, 6.38, 6.03 [06:29:42] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 4.53, 5.78, 5.85 [07:18:11] PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [07:44:13] RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 18 seconds ago with 0 failures [07:57:21] [02puppet] 07Universal-Omega closed pull request 03#3841: varnish: remove Content-Security-Policy header - 13https://github.com/miraheze/puppet/pull/3841 [07:57:23] [02puppet] 07Universal-Omega pushed 031 commit to 03master [+0/-1/±2] 13https://github.com/miraheze/puppet/compare/03f65abeb01a...405198394586 [07:57:25] [02puppet] 07Universal-Omega 034051983 - varnish: remove Content-Security-Policy header (#3841) [07:57:28] [02puppet] 07Universal-Omega deleted branch 03varnish-csp [07:57:29] [02puppet] 07Universal-Omega deleted branch 03varnish-csp - 13https://github.com/miraheze/puppet [07:57:50] [02puppet] 07Universal-Omega closed pull request 03#3836: monitoring: add more wildcard SSL monitoring - 13https://github.com/miraheze/puppet/pull/3836 [07:57:52] [02puppet] 07Universal-Omega deleted branch 03monitoring-ssl - 13https://github.com/miraheze/puppet [07:57:53] [02puppet] 07Universal-Omega deleted branch 03monitoring-ssl [08:01:12] [02puppet] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/puppet/compare/405198394586...631c19c15cdc [08:01:15] [02puppet] 07Universal-Omega 03631c19c - csp: add nexttide.org [08:19:42] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.32, 6.33, 5.60 [08:23:42] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 5.52, 6.23, 5.76 [08:38:15] [02ssl] 07Universal-Omega pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/69ee1195d9d4...bf1e65c2c275 [08:38:16] [02ssl] 07Universal-Omega 03bf1e65c - Add nexttide [09:35:47] PROBLEM - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is WARNING: WARNING - NGINX Error Rate is 55% [09:37:47] RECOVERY - cp36 HTTP 4xx/5xx ERROR Rate on cp36 is OK: OK - NGINX Error Rate is 32% [09:43:36] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.46, 6.76, 5.87 [09:46:05] PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [09:51:33] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 5.57, 6.54, 6.22 [10:01:34] guys [10:01:44] I think something might be a tad bit broken [10:02:01] I think stuff might be overloading [10:02:04] just a hunch [10:02:24] naaaah it's fiiine [10:13:56] RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 31 seconds ago with 0 failures [10:36:13] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.18, 6.30, 5.79 [10:40:12] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 6.60, 6.52, 6.02 [12:10:10] [02ErrorPages] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ErrorPages/compare/7366fa181abe...1735964a9887 [12:10:11] [02ErrorPages] 07translatewiki 031735964 - Localisation updates from https://translatewiki.net. [12:10:13] [02ImportDump] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ImportDump/compare/a735eeb1ecb2...e778791db6d0 [12:10:15] [02ImportDump] 07translatewiki 03e778791 - Localisation updates from https://translatewiki.net. [12:10:16] [02WikiDiscover] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/WikiDiscover/compare/500dfb0373f3...61869c2827f9 [12:10:17] [02WikiDiscover] 07translatewiki 0361869c2 - Localisation updates from https://translatewiki.net. [12:10:19] [02MirahezeMagic] 07translatewiki pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/MirahezeMagic/compare/b954480d12a9...5e6efedbe61f [12:10:22] [02MirahezeMagic] 07translatewiki 035e6efed - Localisation updates from https://translatewiki.net. [12:11:03] miraheze/ErrorPages - translatewiki the build passed. [12:12:42] miraheze/MirahezeMagic - translatewiki the build has errored. [12:16:21] miraheze/WikiDiscover - translatewiki the build passed. [12:21:11] miraheze/ImportDump - translatewiki the build passed. [12:24:13] !log [@test151] starting deploy of {'folders': '1.42/extensions/MirahezeMagic'} to test151 [12:24:14] !log [@test151] finished deploy of {'folders': '1.42/extensions/MirahezeMagic'} to test151 - SUCCESS in 0s [12:24:18] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:24:23] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:24:23] !log [@test151] starting deploy of {'folders': '1.43/extensions/MirahezeMagic'} to test151 [12:24:24] !log [@test151] finished deploy of {'folders': '1.43/extensions/MirahezeMagic'} to test151 - SUCCESS in 0s [12:24:29] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:24:33] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:32:44] !log [@mwtask181] starting deploy of {'folders': '1.42/extensions/MirahezeMagic'} to all [12:32:50] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:32:55] !log [@mwtask181] finished deploy of {'folders': '1.42/extensions/MirahezeMagic'} to all - SUCCESS in 10s [12:33:00] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:37:23] !log [@mwtask171] starting deploy of {'folders': '1.42/extensions/MirahezeMagic'} to all [12:37:28] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [12:37:32] !log [@mwtask171] finished deploy of {'folders': '1.42/extensions/MirahezeMagic'} to all - SUCCESS in 9s [12:37:37] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [13:16:44] PROBLEM - wiki.mahdiruiz.line.pm - LetsEncrypt on sslhost is CRITICAL: Temporary failure in name resolutionHTTP CRITICAL - Unable to open TCP socket [13:46:43] RECOVERY - wiki.mahdiruiz.line.pm - LetsEncrypt on sslhost is OK: OK - Certificate 'wiki.mahdiruiz.line.pm' will expire on Fri 29 Nov 2024 07:59:27 PM GMT +0000. [14:12:52] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.56, 6.51, 5.71 [14:14:51] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 6.43, 6.61, 5.86 [14:24:46] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.02, 6.74, 6.18 [14:26:45] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 5.41, 6.11, 6.01 [14:42:38] PROBLEM - os162 Current Load on os162 is WARNING: LOAD WARNING - total load average: 7.03, 6.08, 5.67 [14:44:38] RECOVERY - os162 Current Load on os162 is OK: LOAD OK - total load average: 6.52, 6.04, 5.69 [14:45:11] PROBLEM - ns2 Puppet on ns2 is CRITICAL: CRITICAL: Failed to apply catalog, zero resources tracked by Puppet. It might be a dependency cycle. [15:13:42] RECOVERY - ns2 Puppet on ns2 is OK: OK: Puppet is currently enabled, last run 47 seconds ago with 0 failures [16:19:22] [02ssl] 07redbluegreenhat pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/bf1e65c2c275...a0fde92dc498 [16:19:24] [02ssl] 07redbluegreenhat 03a0fde92 - use the Miraheze CF origin cert on themanaworldwiki [16:21:13] other than CF on *.miraheze.org, there are no more users of the Sectigo miraheze.org wildcard anymore [16:37:25] I could make that zero usages easily [16:48:15] but the Sectigo cert includes the Sectigo Trust SealTM!! [16:48:27] You ain't getting that from an LE cert 😎 [16:49:11] It will change to Google soon I think [16:49:21] Most of the custom domains are google trust services [16:50:32] What’s sectigo [16:50:37] Another CA? [16:50:45] ..why is everything here CA [16:50:51] it also is has the Fastest Issuance, a $500,000 SSL Certificate Warranty, and is compatible with the leading browsers! [16:51:10] 🤑 [16:51:10] Honestly I don't know why you'd want to get rid of it ❓ [16:51:28] @bluemoon0332 stupidity aside, shall I withdraw the Sectigo cert? [16:51:50] In fact I'll formally propose we buy the $879 OV cert!! [16:51:59] well we don't really need it [16:52:27] I don't really know why it was added to CF to begin with [16:52:30] It will switch to Google Trust Services btw [16:53:29] !log withdraw Sectigo Modern Cert from Cloudflare, switching to Universal SSL [16:53:34] Logged the message at https://meta.miraheze.org/wiki/Tech:Server_admin_log [16:53:40] @bluemoon0332 it's fine [16:55:53] @bluemoon0332 you can drop it from ssl now [16:56:24] miraheze.com, miraheze.wiki, orain.org, wikitide.com can now be switched to the miraheze.org origin cert [16:56:36] Too [16:56:39] @bluemoon0332 [16:57:54] [02dns] 07RhinosF1 opened pull request 03#603: Delete zones/wikitide.com - 13https://github.com/miraheze/dns/pull/603 [16:58:10] [02dns] 07RhinosF1 opened pull request 03#604: Delete zones/miraheze.com - 13https://github.com/miraheze/dns/pull/604 [16:58:38] [02dns] 07RhinosF1 opened pull request 03#605: Delete zones/miraheze.wiki - 13https://github.com/miraheze/dns/pull/605 [16:58:55] [02dns] 07RhinosF1 opened pull request 03#606: Delete zones/orain.org - 13https://github.com/miraheze/dns/pull/606 [17:14:30] they don't seem to be in certs.yaml? [17:14:50] The certs for them must be deployed somehow [17:14:52] and as far as I know the only thing in orain.org which is meta.orain.org is just a regular custom domain [17:15:04] That can use the custom domain [17:15:20] So can the ones in redirects.yaml [17:16:10] Anything using a certificate for them domains can switch to origin cert as of now [17:16:26] It's been 48 hours [17:16:38] I was too busy yesterday evening to do it [17:17:15] [02ssl] 07redbluegreenhat pushed 031 commit to 03master [+0/-0/±1] 13https://github.com/miraheze/ssl/compare/a0fde92dc498...d262b32f8720 [17:17:18] [02ssl] 07redbluegreenhat 03d262b32 - Swift orain.org to miraheze-origin-cert [17:18:15] miraheze/ssl - redbluegreenhat the build has errored. [17:18:33]