[01:01:57] ahh Consul is so nice why have I never used this before [01:05:57] what's consul in this context [01:11:37] HashiCorp Consul [01:12:46] we using it? [01:12:51] I am personally [01:12:55] Miraheze doesn't [01:13:06] telepedia? [01:13:13] Aye [01:13:27] I heard about consul like yesterday [01:13:36] Really [01:14:16] https://youtu.be/VjR8OJtGQLM [01:14:20] here [01:15:06] Interesting [01:15:19] i love this youtuber [01:15:23] make really nice videos [01:18:00] His voice is asmr [01:23:06] real! [06:01:36] > It may be board related, particularly the front board as it's a board built into the front of the chassis that contains those sensors (along with some other stuff) [06:16:16] [1/2] Not sure if this is the right channel. [06:16:17] [2/2] If you are planning on updating the Citizen skin, there are some HTML changes on the menu of Citizen that will probably require purging page cache if any is used on Miraheze. They don't happen often but it was necessary sadly [06:18:49] From the last update it seems that it would require updating the localisation cache too to add the new client preferences [10:15:05] i wonder, in https://www.mediawiki.org/wiki/Manual:$wgShowExceptionDetails, what does it mean by "This should only be used for debugging, as it may reveal private information in function parameters due to PHP's backtrace formatting" [10:20:52] BlankEclair: exactly what it says [10:21:07] i probably should've phrased that better [10:21:14] what is "private information" here [10:21:15] Also morning [10:21:23] Anything that could be passed to a php function [10:21:24] (yeah, that question definitely should've been better) [10:21:30] ah shucks [10:21:32] Private user data, passwords [10:21:51] also mornin' [10:21:53] (Not login passwords, the stuff we keep in PS.php) [10:22:07] yeah it could basically just be about anything [10:22:14] Ye [10:22:36] i wonder if there could be a watered down version where it doesn't show arguments [10:22:51] though this is probably more of a wikimedia proposal than anything [10:22:51] Maybe [10:22:54] mediawiki* [10:23:02] I'm not sure it'd be helpful to most users anyway though [10:23:14] yeah but i want logs :( [10:23:18] If you over expose information, confused users are more likely to solutionise [10:23:24] oh right [10:23:32] Which wastes time [10:23:43] I think beta exposes some logs [10:23:50] yeah it has that enabled [10:23:55] Ye [10:24:02] Cause beta is basically a security and privacy risk [10:24:06] ...but femiwiki is disabled for 1.42 so i can't get the stack trace that way [10:24:12] Ah [10:24:14] Sucks [10:24:18] and trying to set the skin up on my own wiki did not reproduce [10:24:18] We need an MWE [10:24:35] s/my own wiki/my local mediawiki install/ [10:24:54] the mediawiki and wikimedia naming scheme is kinda clever, but also bloody annoying when you accidentally type one instead of the other [10:25:56] Heh [10:26:08] * RhinosF1 is currently trying to be pragmatic and use sense at work [20:53:57] The replacement for graph will be called charts and based on apache echarts [20:54:38] Oh I love echarts [20:55:25] Oh? They're just going to make a new one? I suppose that makes sense, all things considered. [20:55:53] Based on https://phabricator.wikimedia.org/T369950 [20:57:42] Coming soon to a Miraheze wiki near you [21:02:24] WMF loves an Apache project [21:02:41] Your getting graph back soon [21:03:05] Although it's a WMF project so Roan's kid could quite possibly be starting high school before it gets to us [21:03:39] i made a coming soon clip on a free video generator but i dont wanna login to export [21:04:38] Ive never used graph in my life tbf [21:05:05] It's been disabled a while [21:05:09] For many security issues [21:05:10] Once i asked in the wmf discord to be added to the ticket for the security issue in the original ticket snd everyone bit my head off over it [21:05:22] @originalauthority why didn't you just ask me [21:05:37] I didn't know you had security access back then [21:05:38] also why they bite your head off [21:06:07] Starting a new extension is probably the better way to go [21:06:19] We know how score went, they fixed the issue and more just kept coming [21:07:00] We still haven't got score back [21:07:11] I don't think [21:07:50] I just tried to find the convo but discord search sucks. They were basically saying that it would be reckless to add me because the extension is still enabled on some wikis and i was like okay its been nearly a year since the security notice went out [21:08:03] Not like i was gonna try and hack the Chinese wikipedia is it [21:08:33] I used to ask Scott [21:08:38] He's pretty chill [21:08:47] Or mutante [21:10:13] Meh not like I was gonna try fix it anyway i was just interested what the issue was [21:10:40] I remember score. You'd pretty much have to rewrite lilypond from scratch to make it secure. [21:12:38] They ended up making shellbox to sandbox it [21:12:44] But we've never deployed shellbox [21:13:15] @orduin our best guess for cloud15 is the board [21:13:20] So that's going to be fun [21:13:31] If we need the DC to arrange a motherboard swap with Dell [21:13:40] They'll probably want bios and firmware upgrades first [21:14:22] Well we'll need to deploy shellbox anyway for Charts [21:14:48] I don't think @cosmicalpha could work it out [21:14:55] Do we own the servers at the DC? I Thought they we moved away from Colocation? [21:15:55] We don't [21:16:06] But we'll still need the DC to arrange a hardware repair [21:16:14] Or at least I'm fairly sure the DC own them [21:16:54] Whether we own it or not, it's still got to be fixed