[00:35:48] Can some stack trace this error reported in this ticket please? https://issue-tracker.miraheze.org/T13453 [00:40:43] oki [00:43:47] aeywoo: https://issue-tracker.miraheze.org/T13453#270572 [01:05:05] Danke, I'll try to figure this out now. [01:05:13] yw ^_^ [01:12:09] @blankeclair can you get me the Special:Version information from https://alcolois.miraheze.org/wiki/Special:Version please? [01:12:16] I can't view it cause I don't have global rights to see private wikis. [01:12:59] how much info do you want? [01:13:07] and reason? [01:14:12] [1/2] I'm making a Phabricator ticket for this issue with Page Schemas, and can you just grab all this information? [01:14:12] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1358973168748068984/image.png?ex=67f5c9e3&is=67f47863&hm=408d6e23f17f164638cf7ad51dc8a03ecf96c9cd1b3ec0be781bea750d913a86& [01:14:17] And the version of Page Schemas and SMW being used? [01:14:52] I don't expect Special:Version for their wiki to have much of a difference in information, but you never know :3sKaedeShrug: [01:22:11] Also, those are from Mirabeta btw. [01:28:02] [1/11] MediaWiki: 1.43.0 (fc1759b) 18:31, 21 January 2025 [01:28:03] [2/11] PHP: 8.2.28 (fpm-fcgi) [01:28:03] [3/11] ICU: 72.1 [01:28:03] [4/11] MariaDB: 10.11.11-MariaDB-deb12-log [01:28:03] [5/11] wikidiff2: 1.13.0 [01:28:04] [6/11] LuaSandbox: 4.1.2 [01:28:04] [7/11] Lua: 5.1.5 [01:28:04] [8/11] Pygments: 2.17.2 [01:28:05] [9/11] Elasticsearch: 7.10.2 [01:28:05] [10/11] Page Schemas: 1.0 (53e52f6) 13:27, 10 March 2025 [01:28:05] [11/11] Semantic MediaWiki: 5.0.1-alpha [01:32:24] Tada: [T391307](https://phabricator.wikimedia.org/T391307) [01:32:26] Thanks. [01:32:39] yw ^_^ [10:38:08] @paladox hey, you made patches to PageSchemas for 1.44, are you able to backport those to 1.43 please? They're causing the same issues as specified in this ticket. [10:46:33] They shouldn’t be causing the same issue [10:46:38] It’s a 1.44 only issue [10:48:04] I don’t feel like backporting a patch that changes what compat level it supports. Doing it for 1.44 was fine because it wasn’t realised yet. But also only if necessary. [10:51:14] Unless the method thing is needed for 1.43 in which case you can always do the patch and I can merge [10:51:30] Well, we're getting these errors: `SQL query did not specify the caller (guessed caller: PSEditSchema::execute): SELECT pp_value FROM `page_props` WHERE pp_page = 411 AND pp_propname = 'PageSchema' LIMIT 1` [10:51:41] I don't know how to use gerrit. [10:51:41] But anyways yaron extensions usually are master only as he keeps backwards compat. [10:51:48] Those aren’t errors. It’s a warning [10:52:09] Well, we also have this one: `TypeError: Cannot assign null to property SD\DbService::$dbw of type Wikimedia\Rdbms\DBConnRef`. [10:52:23] That’s an error [10:52:34] Yes, it causes an exception that breaks that page. [10:53:02] You’ll have to post the full output [10:54:30] It's in the ticket. [10:54:57] [T13453#270572](https://issue-tracker.miraheze.org/T13453#270572) [10:57:19] It's also in the Phabricator task: [T391307](https://phabricator.wikimedia.org/T391307) [10:59:32] Oh [11:03:00] It seems to be an issue between SemanticDrilldown and PageSchemas, not sure if it's a SemanticDrilldown issue to report about, but SemanticDrilldown drops PageSchemas support in Version 4.0.0, which is likely for REL1_44. [11:19:37] https://github.com/SemanticMediaWiki/SemanticDrilldown/pull/111 [11:22:34] Thank you, I'll update both tickets now. [11:56:30] we use the master branch https://github.com/miraheze/mediawiki-repos/blob/main/mediawiki-repos.yaml#L885 [11:58:19] oh in a different place [11:59:45] https://gerrit.wikimedia.org/r/c/mediawiki/extensions/PageSchemas/+/1135014 [12:00:59] @rhinosf1 scariest thing I’ve read all day https://phabricator.wikimedia.org/T391270#10720244 [12:02:25] i mean, it makes sense? [12:02:37] i honestly expected sul3 to be a completely separate service from mw [12:05:19] That's not scary [12:22:56] I was expecting to read one of the worst XSS vulnerabilities to be discovered in extension since Graphs or even Widgets. [12:23:24] Oh hey, they merged it. [12:24:16] Can someone pull the new version of the master repo for SemanticDrilldown? [12:24:30] it's done [12:25:26] Can you check https://alcolois.miraheze.org/wiki/Cat%C3%A9gorie:Test-schema and see if it still gives an error? [12:25:36] I can't, because the wiki is "private" [12:25:58] i see no error [12:26:19] Awesome, and I'm assuming Page Schemas is working as intended? [15:29:06] @orduin hi are you around [21:14:58] [1/2] does anyone know what this means 💔 [21:14:58] [2/2] https://cdn.discordapp.com/attachments/1006789349498699827/1359275351204958339/yk6H9pk.png?ex=67f6e351&is=67f591d1&hm=872a76a8eb4f4cf5ae867c9cd110723ac3cbb66acece8450c579395ed07ebac5& [21:15:15] i want to use a 2k resoution of a pretty large image [21:52:06] No idea what caused this but probably worth making a ticket on Phorge? [21:52:19] also wow, does this mean MediaWiki stack/Miraheze uses firejail for sandboxing? 👀 [21:54:45] https://github.com/miraheze/mediawiki/blob/master/includes/shell/firejail.profile oh, it does, that's fascinating [21:57:31] hm? [21:59:19] alr [22:00:04] pixldev: just surprised to see MediaWiki using firejail as solution for sandboxing. I use it for sandboxing my Firefox instances. [22:05:47] Here at MediaWiki & Co. we only use the most random and questionable software in our stacks [22:15:06] Yeah, I've seen it being discussed as insecure in the past for various reasons. Unsure how true that is because computer security of this level is over my head [22:20:06] btw, is my assumption that database name is not strictly equivalent to wiki's *subdomain*.miraheze.org correct? [22:21:09] it’s equivalent to `wiki` [22:21:19] so meta.mh.o -> metawiki [22:21:23] always? no exceptions? [22:21:45] On miraheze.org yes [22:22:08] i think we literally get the db by that, subdomain, slap wiki on the end, thats the db your using [22:22:16] I see, okey, thanks. So my assumption was incorrect :P [22:23:54] Asking because for Wiki-Bot's rcscript we use IRC feed that uses database name. However wikis are stored (currently) as URLs and it regexes the dbname to match the subdomain on miraheze.org. Though I have MR to change it a little so it supports custom domains [22:24:18] Was wondering if it was very broken in some cases or not [22:24:30] but I guess it wasn't then [22:24:43] good, I don't have to hurry up with that MR (not that I already were in a hurry) [22:46:01] [1/3] we want to host a fedi instance with the handles being, e.g. @quotes@rainverse.wiki [22:46:01] [2/3] per https://docs.gotosocial.org/en/latest/advanced/host-account-domain/, we'll need to redir `rainverse.wiki/.well-known/(webfinger|host-meta|nodeinfo)` -> `gts.rainverse.wiki` [22:46:02] [3/3] i presume that's done in cloudflare? [22:48:42] cc @paladox ^ [22:48:58] i can set it up (since the instance is not up yet) [22:50:06] i'm not entirely sure [22:50:27] oh? [22:52:05] just realised i didn't copy https://github.com/miraheze/puppet/blob/main/modules/varnish/templates/mediawiki.conf.erb#L217 to haproxy [22:53:38] 👍 [22:53:49] oh right, i forgor that we have path redirects in miraheze/ssl [22:54:11] oh [22:54:57] i guess that's legacy? I dunno how we do it using the miraheze-origin cert? [22:55:42] oh hmm, redirects.yaml takes over a whole domain [22:57:20] see also: https://issue-tracker.miraheze.org/T13039#269936 [22:58:02] oh ok [22:58:39] is it okay then? [22:58:51] yeh redirects still work [22:58:56] oki ^_^ [22:58:58] guess you do do them in cf