[07:14:56] Sysadmin did not want to apply my ReplaceText extension patch, so now I'm back to looking at it (and it was rather incomplete as I did not consider maintenance/replaceAll.php) [07:15:08] Is there any way I can drop results from an IResultWrapper ? [07:16:16] as now I had to resort to creating an array: https://phabricator.wikimedia.org/T313148 but it just leads to pointless renovation of existing code [09:10:33] hmm, I built a new query based on the page_ids: https://paste.simplylinux.ch/view/3d5c4520 [09:10:59] I should submit a patch to Gerrit later [09:15:20] buovjaga: I think the generally the preferred approach would be to implement a Hook there, to allow the Translate specific code to stay in the Translate extension [09:15:39] although people tend to be less picky about that for code that is inside another extension [09:22:22] uh oh. looks like a big outage ? [09:22:32] even wikitech seems down [09:22:56] TheDJ1626[m]: up for me [09:23:55] k. then esams is down.. [09:23:56] https://www.wikimediastatus.net/ [09:23:59] check the error rate [09:25:05] anon access still seems to work. prolly due to being in frontend cache [09:25:41] s/../ perhaps. or something else creating local effects/ [09:26:11] Huh, weird. The graphs seem like its app servers, but my connection is still fine [09:26:18] status page is updated now. [09:27:48] bawolff: ok, but I don't know how to do that [09:28:17] so I was hoping to do it in the wrong way and make someone annoyed enough to do it the right way [09:28:22] * bawolff enjoys trying to see if i can figure out what is going on before the SRE experts can :) [09:28:39] usually the answer is i can't, which is why they're the experts ;) [09:29:16] buovjaga: Honestly, I'm not even sure what the correct way to add a custom hook in an extension is anymore. The old way was calling Hooks::run [09:29:20] logstash and grafana are also down for me, so it's more towards edge it seems. [09:29:53] * towards edge network it seems. [09:31:42] I suppose some sort of peering/network connectivity issue would make sense. esams traffic is reduced but not totally according to the graph [09:35:58] and we are back [10:09:32] bawolff, buovjaga: I'm not sure either, but maybe like this: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Translate/+/889529 [10:10:20] Probably [10:10:42] Although it seems like most extensions have not been converted to the new form, so maybe Hooks::run is still acceptable in extensions [10:11:42] It is very much, or the more modern alternative of MediaWikiServices::getHookContainer()->run() [10:12:08] The interfaces are optional to provide static types [10:14:16] buovjaga: btw you cannot use title::newFromText( $row->page_title), that drops the namespace, use newFromRow or makeTitle [10:32:35] thanks [10:39:54] buovjaga: or if you have a DB row object, Title::newFromRow [10:45:20] yes, it worked: $title = Title::newFromRow( $row ); [11:26:32] I now have a Wikimedia dev account, I added an SSH key into Gerrit, saved, but I can't figure out why permission is denied: https://paste.simplylinux.ch/view/7304855f [11:27:00] We use Gerrit for LibreOffice and I even advise newcomers all the time in this, but I don't understand what is wrong in this case [11:27:48] buovjaga: Its karam to experience the newcomer issues, so as to remember what it is like ;) [11:28:07] I will embrace it [11:29:15] buovjaga: Just to confirm, you added the ssh key to gerrit (Since i think there is a different system that also accepts ssh keys related to wikimedia dev account) [11:29:18] ? [11:29:41] yes, Gerrit [11:30:02] and got the email confirmation [11:33:04] buovjaga: What's the shell name you used when registering? [11:33:42] bawolff: ah, thanks, I thought I should use my user name. Shell name works [11:33:59] yeah, the username vs shell name thing is super confusing [11:34:06] per https://www.mediawiki.org/wiki/Gerrit/Tutorial [11:34:10] Because you log in with your username from the web interface [11:34:17] Replace gerrituser by your username as shown in your Gerrit settings [11:34:41] Ah, so i see you've discovered our super helpful and never incorrect tutorials ;) [11:34:44] and indeed I see my shell name as the username in gerrit [11:34:53] well it was technically correct :) [11:35:13] The best kind of correct! [11:36:33] Hello, bnwiki is now read-only. Some users can edit and some can't. Can anyone tell me if any maintenance work is going on! [11:44:06] Yahya: Umm, not that i've heard. What happens when they try and edit. Is there a specific error message? [11:44:36] Yahya: oh wait, i see some dev discussion about this [11:45:07] Error message: The wiki is currently in read-only mode. [11:45:15] Yahya: it sounds like there was some test of setting things read only that was not supposed to actually set it read only, but actually did [11:45:21] It should clear up in a few minutes i think [11:46:22] A user reported on my talk page a while back that this has been happening for hours. [11:47:26] Yahya: So devs just took the server they think was causing the problem out of rotation. Have you seen any errors since about 2 minutes ago? [11:48:22] Hmm, they are still seeing errors, so maybe they haven't fixed it [11:48:38] Unclear, but people are definitely looking into it and trying to fix it [11:51:11] Nikerabbit, bawolff: here it is https://gerrit.wikimedia.org/r/c/mediawiki/extensions/ReplaceText/+/891258 [11:58:38] now it's time for my bug streaming: https://lists.freedesktop.org/archives/libreoffice-qa/2023-February/011379.html [12:00:30] phpcs is going to probably complain about whitespace, just FYI [12:00:41] Did my explanation about what hooks are make sense? [12:01:15] Hmm, that's an interesting idea (livestreaming triage) [13:10:16] bawolff3779[m]: re: hook explanation, so you're saying ReplaceText would feed $result and the handful of other vars to a function in Translate and use the returned result? [14:13:54] buovjaga: I think a simple solution would be to pass a title or list of titles via the hook, and allow extensions to remove from the list [14:38:33] right [17:36:16] Is there some way (an extension or some other way to tackle this) that would allow the wiki to disambiguate similarly named pages based on a user defined context? Like a category filter that the use can quickly select (e.g. a drop-down menu) which then controls which version of something is being fetched. Of even fetch entries about the same concept in different languages. [18:15:02] Im on mobile now, but im getting db errors on mw.org for the project helpdesk.. [18:15:02] https://www.mediawiki.org/w/index.php?title=Topic:Xd35o6keduq9pslt&mobileaction=toggle_view_desktop [18:16:21] Not on all views. Might be that a rollout/rollback is in progress related to this [18:17:02] A database query error has occurred. This may indicate a bug in the software. [18:17:02] [c5d2980c-e0fe-486b-ba69-7dbecf736fec] 2023-02-22 18:16:38: Fatal exception of type "Wikimedia\Rdbms\DBQueryError" [18:18:49] huh, yes, opening any topic directly gives the error. However, the Support Desk itself works fine... [18:20:41] Strange. I got to a topic page from a notification and it loaded fine. After refreshing the page once, it gives the error consistently... [18:23:50] I get a db error on the support desk page but not the topic link I just got sent [18:24:59] Amir1: ^^ [18:25:14] let me check [18:25:16] let's see [18:25:23] no flow changes in this train at least [18:25:39] now I wonder if taavi has got a watch word on Amir :thinking: [18:25:49] I don't [18:25:50] sigh [18:25:53] let me fix it [18:26:15] grant issue apparently, I'll leave that to Amir [18:26:53] Izno: can you try again? [18:27:21] yup, I'm good. TheDJ1626[m] ? [18:28:51] Seems to work now, indeed [18:29:07] I was able to even send a new message [18:30:34] Thx Amir ! 😉 [18:30:53] Sorry for the mess [18:31:55] Better mw.org than en.wp [18:35:20] haha, yeah, the flowdb grants were missing [18:36:34] TheDJ1626[m], haha, you think it's still deployed on en.wp [18:37:33] No, just a general rule [18:40:16] In well aware that its not on en.wp, Theres after all, a reason i left after the fram ban got overturned. [18:41:17] yes, and it was also a joke on my part 😛 [19:09:11] "Is there some way (an extension..." <- Is there maybe another mediawiki related forum or documentation to get some hints on how to do this? [19:23:23] SeriousFun01[m], what problem are you trying to solve? there are some extensions that support multi-language wikis that do something similar to the back-half of that request (nb it didn't display in IRC but did in Discord) [19:23:56] https://www.mediawiki.org/wiki/MediaWiki_Language_Extension_Bundle and particularly https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:Translate [19:26:21] I think there is a custom setup of that particularly for zh.wikipedia [19:28:06] but otherwise, no, things like "category filters" probably don't exist. that direction takes you toward the semantic MediaWiki offerings, like the Semantic MediaWiki and Cargo extensions [19:28:27] which can be poor-man's replicated in the category system with some category intersection [19:37:39] "SeriousFun01, what problem are..." <- the core problem is how to serve intuitively pages for concepts that use the same name to mean different things depending on context. Wikipedia faces this problem as well and has the disambiguation page (example: Law) https://en.wikipedia.org/wiki/Law_(disambiguation). The intuitive solution would be to provide to the wiki the context (e.g., somewhere in the post URL to have the string [19:37:39] "Legal" or "Physics" and the wiki serves the correct page. (Instead of creating a page with title "Legal - Law", "Legal - Physics" etc. [19:38:24] something like that might exist, but I doubt it [19:38:52] Wikidata goes that direction, but that's an entirely different ballgame to what you're considering [19:43:57] "Wikidata goes that direction..." <- minimally it needs some db modification (to add specific context to each page - or default to a "global") and the skin needs to expose the options. It does not sound too difficult so probably people have done it internally but scanning through published extensions I don't see something suitable. Thanks for reacting [19:44:44] "does not sound too difficult" is always a miss in MediaWiki development :) [20:49:45] SeriousFun01[m]: cache fragmentation is your big issue with that particular route, unless you handle it 100% via javascript [20:51:12] for the URL-based solution, I don't see any difference between what you propose and just making a page named that, UX-wise