[00:03:47] oh damn PageImages doesn't work with Parsoid parses ugh [07:48:11] nothing works with parsoid [07:48:17] that's the magic of parsoid [08:03:55] [1/2] New access request ๐ŸŽ‰ [08:03:55] [2/2] https://issue-tracker.miraheze.org/T16436 [11:08:24] @rhinosf1 db161 crashed it seems can you depool? [11:08:56] I can reboot if you can depool [11:10:46] Or @jenny_on_wiki ? [11:11:20] I can depool yeah [11:11:25] Thanks! [11:11:35] is it still mwtask181 to depool or did that change recently [11:11:45] Yeah [11:12:01] edit the config in LS and deploy to all servers with --force [11:12:43] just `$wgDatabaseClustersMaintenance = ['c2'];` right [11:12:48] Yep [11:12:58] Please ping me when done and I will reboot. [11:14:26] congrats guys [11:14:35] indivudials [11:14:42] users on the internet [12:25:37] @posix_memalign @cosmicalpha https://bluemoon.rhinosf1.com/ now gets as far as test151 [12:27:10] nice [12:28:58] https://meta.mirabeta.org/wiki/Special:ManageWiki/core/customdomainwikibeta looks fine [12:29:08] @cosmicalpha ^ [12:29:18] Nice [12:30:38] woo https://bluemoon.rhinosf1.com/wiki/Main_Page [12:30:42] it works ish [12:31:05] InvalidArgumentException: Unknown cluster 'echo' [12:31:10] so the db is broken [12:31:32] @cosmicalpha wtf is beta whining about on my test wiki [12:31:52] we probably check if the hostname is mirabeta.org somewhere? [12:34:17] i don't see anything in https://github.com/search?q=repo%3Amiraheze%2Fmw-config+mirabeta.org&type=code @cosmicalpha [12:38:18] [1/2] https://github.com/miraheze/mw-config/blob/d1e57ee86dbce8dde6a635b954d9cadf3d7cbb02/initialise/MirahezeFunctions.php#L354 [12:38:19] [2/2] might be related [12:38:52] bugger [12:39:16] I should get some sleep. Almost 6AM [12:39:55] I will wake up in about 1.5 hours anyway. [12:39:59] https://github.com/miraheze/mw-config/pull/6623 [12:40:12] @cosmicalpha i will do ^ [12:41:18] just change isBeta to `str_starts_with( wfHostname(), 'test' )` I think? [12:41:35] I don't know for sure on other potential side effects though [12:41:48] if somewhere it expects the hostname check or not [12:41:49] no? [12:41:56] Why? [12:42:19] test isn't always in the hostname is it? [12:42:22] wfHostname will return test151 on any domain on beta [12:42:37] oh ye [12:42:43] that does work [12:42:45] ye could do [12:42:49] didn't we used to do that [12:42:59] i will do that later [12:43:04] i have a meeting soon [12:43:09] @posix_memalign https://bluemoon.rhinosf1.com/wiki/Main_Page works [12:43:19] Yeah that's why I am not sure why it is the way it is now. Or if it has some other reason. [12:43:42] I know I made isBeta but I can't remember why it's like that lol [12:45:08] Maybe from before we fully blocked cross connections [12:45:17] Beta used to be accessible from prod [12:45:27] Oh yeah that might've been why [12:45:43] That should be firewalled off now anyway [12:46:15] It actually wasn't done properly until I realized that when doing the ferm -> nftables migration and fixed it btw. [12:46:34] mw-config blocked it but firewall didn't. [12:46:43] It's not built to be perfect yet anyway [12:46:46] Cause Swift [12:46:55] Yeah true. [12:46:58] Otherwise it would be its own network completely [12:47:19] Also bast* [12:47:58] and os, cp but I plan to add beta versions for those anyway. [12:49:01] Anyway I really need to get some sleep [12:50:37] Only 5 years after we created beta [13:27:38] @cosmicalpha https://github.com/miraheze/mw-config/pull/6624 [13:38:19] @rhinosf1 feel free to merge [13:38:22] looks good to me [13:38:48] Will do in a minute then [13:46:46] deployed [19:52:03] Were you talking about the documentation? If so, yes, it could be outdated. [19:54:41] Belatedly done. See https://issue-tracker.miraheze.org/T16441. [19:56:44] We should probably just be bold and do it [19:56:47] And see what breaks [19:57:00] Nice, you could consider adding your thoughts to that task I just made (and perhaps repurpose it). [19:58:48] Or... just use the CSP-Report-Only header? [19:59:03] Ye [20:02:51] It probably does not need to be a priority but that extension looks like something we would benefit from in the long run. [20:45:50] I looked and no I don't [20:50:32] I keep geting HTTP 500 error when trying to upload a avatar [20:55:25] Known issue. [20:55:36] SocialProfile is not fully compatible with MediaWiki 1.46 [20:57:57] Can someone help fix this issue? [21:06:34] Thanks! Will take a look at the CentralAuth issue once I have more time [21:07:26] https://discord.com/channels/407504499280707585/1006789349498699827/1566918725137989703 [21:07:36] [1/2] You'll need to report it to the devs on https://phabricator.wikimedia.org/project/profile/326/ and ask them to fix it. [21:07:37] [2/2] Though I would advise simply removing SocialProfile and replacing it with UserProfileV2. [21:09:28] I need help with that though as itโ€™s complicated [21:09:45] I think we should send out a notification to all wikis using the extension that we are not going to fix SocialProfile issues ourselves (or very unlikely to do so). Any wiki continuing to use it is doing so at their own risk. If it breaks they need to fix the extension themselves (i.e. submit bug reports to Phabricator/patches to gerrit). [21:10:11] If the rest of tech is okay with that. If it ever happens I'll probably link to a draft for everyone else to review anyway. [21:10:47] That would work as I am facing this bug for weeks [21:11:33] I don't exactly like that [21:11:37] But we probably should [21:11:56] Is it a candidate to maybe restrict or add to the description too [21:12:02] Cc @cosmicalpha [21:13:14] [1/2] We already restricted it per https://issue-tracker.miraheze.org/T16010 but some people like it enough to oppose full removal. [21:13:14] [2/2] We have also been recommending UPV2 in the extension help text for a long time. [21:13:57] Ye go for it then [21:14:15] If we already restrict and a few are hanging round, they have a right to know we ain't caring about the extension [22:46:20] hi all, is this the right place to ask for an oauth app to be approved? https://meta.miraheze.org/wiki/Special:OAuthListConsumers/view/2d768755f028a687f03eaa596449ab4d [22:53:24] your oauth callback of "Special:MirahezeOauthCallback" won't work [22:53:32] it's not a special page lol [22:55:03] hmm yes sorry I think I had initially planned to build an extension that added that page or something but I don't actually want to do that (would have to get it approved by miraheze etc) [22:55:14] also why would you use oauth within mediawiki [22:55:18] that defeats the point of oauth [22:55:40] oauth is for connecting external apps to use mediawiki permissions through authorising it to access your mediawiki account which grants a JWT to that app for your account [22:56:20] well not always a JWT but for all intents and purposes [22:58:21] right, I'm thinking of hosting a site like maps.civwiki.org on a separate box, and to tie voting / submissions to their mediawiki account. I'll change the callback url [22:59:07] yeah that makes more sense lol [22:59:22] yeah sorry lol [22:59:41] tbh it's easier to build the app (or at least part of it) before you request it for the callback url so you actually know what it is [23:30:03] I still get the 5000 error [23:40:58] We will not be fixing this ourselves, that is up to the upstream developers. Apologies for the inconvenience but this is not something we control. If a volunteer wants to fix it that works, but otherwise it will just be stalled for a bit. [23:42:32] who is a upstream developer that can fix this? [23:44:07] I don't know if it is actually fixable while maintaining backwards compatibility. [23:45:19] I have been having this bug for weeks [23:48:17] In 1.46, there was some change to a method signature that SocialProfile overrides, I don't know if it can be fixed in a way that is backward compatible but the fix itself should be simple enough. I can look into it later, but we do not commit to fixing or maintaining that extension ourselves at all. [23:48:49] By later I mean tomorrow at the earliest [23:49:11] so tommrow it could get fixed? [23:49:19] Not guaranteed [23:49:44] oh maybe this week? [23:50:44] Not guaranteed. I said I will look, if I can come up with an easy enough fix it will be fixed, if not it will remain stalled until we upgrade to MW 1.47. [23:51:05] ok then [23:51:07] I understand [23:54:06] [1/2] I think you misunderstood what I said. What I was essentially saying is that we will NOT be fixing any issues related to SocialProfile. Bug fixes need to be done by reporting bugs to the people who maintain the extension (which is not us) and submitting fixes to them. [23:54:06] [2/2] A volunteer _might_ look into it but we provide no guarantees.