[17:07:57] https://usercontent.irccloud-cdn.com/file/CWl2yodj/image.png [17:07:59] Interesting [17:10:10] JohnLewis: ^ [17:10:27] I'm guessing something went wrong with the testing [17:11:20] Reception123: nothing we wrong [17:11:40] I'm debugging in production because we lack a suitable non-production environment to work in for this task [17:12:08] RhinosF1: ^ we need to do something about that [17:13:04] JohnLewis: which task [17:13:16] https://phabricator.miraheze.org/T8667 [17:13:18] [url] ⚓ T8667 User groups disappeared | phabricator.miraheze.org [17:13:19] Reception123: yes that's entire point of isolating beta [17:13:40] Yes, Reception123 and JohnLewis please work on isolating betaheze [17:13:42] RhinosF1: well then how could John test what he's testing now? [17:13:58] Reception123: you'd have to have a consistent reproduction case [17:14:13] It should be possible to do anything on beta that you can do on prod [17:14:16] Reception123 : Whatever code John is running only activates for his IP address [17:14:17] Excluding jobs [17:14:20] That's what I do if I need to test in production [17:14:42] job related stuff doesn't work because there's no Redis setup [17:14:45] RhinosF1: I can not reproduce this problem on betaheze at all [17:15:13] JohnLewis: as far as I'm aware it can't be consistently reproduced anywhere [17:15:27] It happens on some languages on some wikis [17:15:28] I am consistently reproducing it currently on the wiki [17:15:42] yeah but it's not something we know how to replicate [17:15:50] Like with x extension it always happens [17:15:52] RhinosF1: it can be on https://planetarium.miraheze.org/wiki/Special:Statistics [17:15:56] [url] Statistics - The Planetarium | planetarium.miraheze.org [17:15:59] Which is the purpose of debugging [17:16:17] JohnLewis: so it doesn't happen with all the same extensions on? [17:16:24] I do not know [17:16:27] No extension in common between every wiki happening [17:16:34] Well that would be where I'd start [17:16:35] If I knew that, I would be further along with debugging than I am [17:16:48] it should be possible on beta to create wikis [17:17:09] Then feel free to resolve the task, it has been open for 2 weeks [17:17:11] Proxy via task is also another possibility [17:17:36] or having a non-prod environment I can use non-isolated as has worked for numerous years is a good possibility [17:18:43] non isolated has caused us to make production spam errors [17:18:58] Because mediawiki versions keep inserting data that isn't backwards compatible [17:19:09] and errors that are very user visible [17:19:59] And so here we are, having a test environment that can't be used for debugging as it was originally intended for, but is dedicated for a specific function of major software upgrades [17:20:21] Therefore, I shall continue doing my work to resolve a task that is not part of my teams work [17:22:23] I need to try CosmicAlpha's PRs to get the proxy via test3 work [17:22:36] So you can access either environment in cases like this [17:22:41] But he's on indefinite leave [17:23:51] How can I access production environments in an isolated beta environment though? If the purpose is to be entirely isolated [17:24:48] Because all isolation is done on the software end [17:25:28] it's purpose is to be entirely isolated and in an ideal world with infinite hardware it wouldn't even use the same cache proxies [17:25:34] And we'd have mwdebug servers [17:25:36] But we don't [17:26:08] Currently the ManageWiki support for more than 1 environment isn't great so you can access either and make the other error [17:26:47] Okay, so until that is possible, I'll remain using production to debug which is a regression [17:27:22] you can just rm -rf /srv/mediawiki/cache/databases.json then use sql php for any wiki in the right cluster [17:27:35] and that will trick it into picking the environment [17:27:49] Which should allow proxying but take beta out for a bit [17:27:56] which is kinda acceptable for now [17:28:23] Or you can fix the regression, rather than placing the expectation on the debugger to do that every time they wish to look at a task, which places an unnecessary burden on people who wish to be kind to volunteer their time to debug tasks [17:29:32] it's extra work but the person being kind to do most of our development is on leave [17:31:22] In such a case, I would personally prefer to revert back from the regression until fixed, but that is not my decision and there is a sufficient easy workaround until such a case the regression is fixed [19:21:52] @Agent: shouldn't a CN be raise for the open RfCs? Specifically the one for Datawiki [19:23:55] ugochimobi: Potentially but that would fall under the jurisdiction of the Stewards, not SRE. [19:46:32] Hello wm-bot96! If you have any questions, feel free to ask and someone should answer soon. [20:07:27] ]Rfc board? [20:22:48] Perhaps it's time for me to dust off the thought of making a few subscribable areas for notifications and simply pushing those for all but extreme cases [20:23:12] ie, rfgs = one notification set, rfcs = another, and so on [20:23:56] What I heard before was that echo is unpleasant at best to customize, but that having areas you can subscribe to (which then can be edited as authorized) would be interesting [20:39:01] Hello TransitusFluvii! If you have any questions, feel free to ask and someone should answer soon. [22:06:27] any advice on getting set up with wikipedia's CS1 system on a new wiki? [22:06:31] Hello Guest9808! If you have any questions, feel free to ask and someone should answer soon. [22:09:03] enterprisey: Citation Style 1? [22:09:15] yeo [22:09:16] p [22:09:38] i.e. I could just copy/paste all the cite ___ templates, but if there's a better way I'd love to hear about it [22:10:05] Special:Version says we have scribunto so we should be able to use the Lua versions, I guess? [22:10:29] that's it though, that's how I did it, I copied all the codes and pasted it [22:10:50] Special:Version says we have scribunto so we should be able to use the Lua versions, I guess? [22:10:50] Yeah [23:58:58] I'm receiving a fatal exception: https://schizoidnightmares.miraheze.org/wiki/Main_Page Appearing as for me: Fatal exception of type "MediaWiki\Storage\NameTableAccessException" [23:58:59] [url] Internal error - Schizoid Nightmares Wiki | schizoidnightmares.miraheze.org