[09:12:56] Can someone tell me from where can I request the wiki database name and site name to be changed? [09:16:26] xaloria45: database name: [[phorge]] [09:16:27] @link [09:16:27] https://meta.miraheze.org/wiki/phorge [09:16:31] site name: Special:ManageWiki [09:18:43] Are you changing the scope of your wiki? Than that has to be asked on [[SR]] [09:18:43]

[09:18:54] Yes [09:21:45] Please request that at [[SR/M]] [09:21:45]

[09:22:15] If approved, you can file it on [[Phorge]] as mentioned above. [09:22:16]

[16:20:51] i got grafana'd on grafana.wikitide.org.... [16:21:29] gg [16:22:21] wait can we do imports on other mwtasks [16:23:31] I'd assume so [16:23:48] we can probably do everything which doesn't require using a canary server [16:24:34] Yeah tasks have access to the full prod environment iirc [16:25:00] Where have you been doing them 181? [16:25:17] i love mwtask181 my beloved [16:25:21] i need no other server [16:25:26] Me too that's the only one I ever use lmao [16:25:26] Mwtask181 does not like the load [16:25:47] aight bet I'll put the other two imports on another one [16:25:48] Idek what the others are [16:26:07] i use mwtask171 sometimes when mwtask181 is overloaded [16:26:18] but most of the stuff I do requires using a canary server so I can only use mwtask181 [16:26:41] did only mwdeploy need canary or mwscript as well [16:26:52] only mwdeploy [16:27:04] the ext/skin/core files are deployed on all task servers [16:27:14] nice [16:27:15] only the staging ones aren't [16:27:32] we have staging files for 1.42 on mwtask171 though [16:29:05] That should be deleted [16:36:46] mwtask171 was once able to deploy things in case of emergencies (aka if cloud18 went down) but I don’t remember why that was deprecated [16:37:19] sounds like all I can is cry and pray that infra is alive when that happens [16:38:27] according to CA it might've been because it was necessary to sync staging between the two canary servers [16:39:00] could make sense [16:39:08] but mwtask171 was meant for emergency config deploys [16:39:10] not full mw deploys [16:39:21] damn when did that CA global DM happen [16:39:27] but if I were to do a full mw deploy, I’d probably do —upgrade-world [16:51:54] We need to probably setup the patches [16:52:24] But ye actually it probably doesn't work well post us not having fixed data on what's deployed [16:52:34] We might need to look at bringing that back [16:52:43] In some way [16:52:47] If we want a failover [16:53:05] why have a failover when you can have a fail [16:58:46] Resilience [18:37:31] I already did when I was cleaning up 1.43 stuff. [18:38:40] Some servers still had 1.40 stuff. [19:01:46] Good [21:23:32] [1/2] @pskyechology fyi it doesn't work on beta [21:23:32] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1416534789694947338/image.png?ex=68c73253&is=68c5e0d3&hm=1a537db340285fb3e34b5d66c3c01bbed686d597f74dc4d783908ede7dc42de3& [21:23:50] i assume either managewiki, the config or the extension hasn't been pulled yet [21:24:03] [1/2] there's also no description [21:24:04] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1416534922344140982/image.png?ex=68c73273&is=68c5e0f3&hm=587612eb2053f35d978482b914c462e1c37df7feaf4df5561b0549d6a196655e& [21:24:27] @abaddriverlol is that specific wiki on 1.44 since i only deployed it to 1.45 [21:24:32] yup [21:24:37] yeah that explains it [21:24:43] lemme deploy to all versions [21:24:48] thx [21:43:00] the error messages are so good aren't they [21:43:03] very informative [21:47:22] iirc there isn't even a log entry unfortunately [21:47:35] at least sometimes [21:47:41] I spent too long debugging one of these errors once [21:48:59] love when the error is "someone forgor" [21:50:53] the error still occurs btw [21:50:59] at [21:51:17] wtf [21:51:19] Expand the public error message and you bloat UI. It should log if SQL is what is failing though (and nothing but SQL causes that message btw) but just a non-deployment not much we can do there. [21:51:46] use --force-upgrade [21:51:55] Maybe the request ID could be shown, like it is being shown for fatal errors? [21:51:58] Would make it easier to check logs [21:52:13] Not a bad idea. [21:52:22] Actually a very good idea. [21:52:51] (That reminds me that I wanted to write a userscript which adds a button to errors that opens a new tab with a graylog search for the request ID) [21:53:03] @abaddriverlol am going on a walk so feel free to [21:54:44] I actually had this done on MediaWikiDebugJS extension I made but I don't know if I ever pushed it. I think I didn't. It just appended a link to errors. But it was in the chrome extension just to have while logged out also as sometimes errors differ if logged out. I will see if I still have it. [21:55:25] Oh nice [21:55:29] Is there a firefox version? [21:55:44] Not yet but I can make it work if you want. [21:56:04] There just hasnt been a huge need yet but I can easily do it. [21:56:19] Sure, that'd be great [21:56:47] Does WikiTideDebug work on Firefox or should I make it work too...cant remember if it does lol. [21:57:38] I have no idea tbh, I've never used it [21:58:15] Ah. I use it to proxy to mwtask servers instead of looking at graylog at all lol. (since $wgShowExceptionDetails is enabled on mwtask) [21:58:31] Oh so you can choose which server should serve your request? [21:58:35] Yep [21:58:38] That's cool [21:59:39] It needs an access key though (just for protection against targeted against single servers) if you need that its on phorge passphrase or something or I can give it too. [22:01:26] The extension is just a wrapper around the X-WikiTide-Debug header. [22:01:50] [1/2] I've tried to install it from a zip file twice with the files either in a subfolder or directly in the zip and firefox doesn't want to install it [22:01:50] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1416544426372894731/image.png?ex=68c73b4d&is=68c5e9cd&hm=cd90d8b192a15dd23ab7ee01be1854ac63d636f9ccc2b0c6c4a9c036f926103a& [22:02:06] Thanks I will make a compat one for it also. [22:02:16] Thx [22:19:31] [1/5] Anyone know what causes this error for phpunit tests: [22:19:31] [2/5] ```php [22:19:31] [3/5] Next PHPUnit\TextUI\RuntimeException: Class "MediaWikiIntegrationTestCase" not found in /DIR/mediawiki/vendor/phpunit/phpunit/src/TextUI/Command.php:101 [22:19:32] [4/5] ``` [22:19:32] [5/5] Winding me up badly ugh [22:20:23] idk if I'm going to sound dumb but I don't have any ccs coding knowledge but I have learned a bit. How do I implement wiki skins & templates or something like that? [22:26:41] do you mean how to create the skin itself or how to style the skin that you're already using? [22:28:08] Basically I went into the extensions and enabled a skin, I don't know if I need to publish it first but I saw nothing changed so I enabled every skin and still nothing. [22:29:04] if you go to your preferences then you can change your skin on the "appearance" tab [22:29:56] you can change your wiki's default skin on Special:ManageWiki/settings [22:30:09] just look up wgDefaultSkin [23:32:24] Special:GlobalContributions appears to be experiencing an error: Fatal exception of type 'Wikimedia\Rdbms\DBQueryError'