User talk:MusikAnimal

From Meta, a Wikimedia project coordination wiki
(Redirected from User talk:MusikBot II)

Wikimedians for Sustainable Development - April 2023 Newsletter[edit]

This is our twenty-sixth newsletter, covering April 2023. This issue has news related to SDGs 2, 4, 5, 6, 11, 13, 14, 15 and 16.

Meetings

Activities

News

Research

New Wikidata properties

Featured content

This message was sent with Global message delivery by Ainali (talk) 19:31, 2 May 2023 (UTC) • ContributeManage subscriptionReply[reply]

MusikBot offline[edit]

Hello, looks like MusikBot has been offline for the last two days. ~~~~
User:1234qwer1234qwer4 (talk)
14:00, 18 May 2023 (UTC)Reply[reply]

@1234qwer1234qwer4 Which tasks are you referring to? User:MusikBot II/TemplateProtector or one of the tasks for other wikis? MusikAnimal talk 06:17, 19 May 2023 (UTC)Reply[reply]
I meant the IRC bot. Sorry! ~~~~
User:1234qwer1234qwer4 (talk)
07:44, 19 May 2023 (UTC)Reply[reply]
Ah okay, restarted :) Of course, nothing in the logs explaining what happened. The main issue here is phab:T306391 and phab:T315729. There isn't a workable solution at the moment to auto-restart whenever the bot dies, which wasn't a problem in the past when we were using the Toolforge grid. That's deprecated now, so until Kubernetes has feature parity, occasionally the bot is doomed to die requiring a manual restart. Anyway, thanks for letting me know! MusikAnimal talk 08:11, 19 May 2023 (UTC)Reply[reply]
Thanks! ~~~~
User:1234qwer1234qwer4 (talk)
19:33, 19 May 2023 (UTC)Reply[reply]

global-search and case sensitivity[edit]

Hi MA.

Freenode • global-search and freenode • global-search give different, case-sensitive results, and converting that to a regular expression seems weird approach. Is there a different syntax that can be used to get case-insensitivity? Seems that with case sensitivity it will be a means to miss things from within {{LinkSummary}} if a spammer plays silly buggers with us.  — billinghurst sDrewth 06:54, 29 May 2023 (UTC)Reply[reply]

@Billinghurst As far as I know this is only possible using a regular expression. However, since you're doing an exact match with double quotes, it's actually doing a regex search anyway behind the scenes. I should maybe document this or something. Anyway, despite the warning, a regex search as specific as this one should perform just fine. On my end it took only ~30 seconds. Best, MusikAnimal talk 04:10, 1 June 2023 (UTC)Reply[reply]

Recent MoreMenu adjustment[edit]

I know you're having fun with skinning stuff, but your recent edit to MM caused phab:T338668. Can you adjust the selector? Izno (talk) 19:44, 12 June 2023 (UTC)Reply[reply]

Eh, I wouldn't call it "fun", hehe :) I've deployed another hotfix. It should take effect in ~10 minutes (after ResourceLoader does its thing). Thanks for reporting, MusikAnimal talk 19:51, 12 June 2023 (UTC)Reply[reply]

New quirk in globalsearch, title parameter now required[edit]

It seems that searches are requiring the use of the title= parameter whether it is needed or not. I don't use the parameter in {{LinkSummary}} and it throws an error Typed property App\Model\Query::$titlePattern must be string, null used

Yet if I do the same "search" with appending &namespaces=&title= as a default search does, then it works fine. Happy to change it over if required, thought that I would flag the quirk first.  — billinghurst sDrewth 22:34, 6 July 2023 (UTC)Reply[reply]

Should be fixed now. Thanks for letting me know :) MusikAnimal talk 03:07, 7 July 2023 (UTC)Reply[reply]

Global search: title pattern[edit]

Looking at the global search form, it says Title pattern: (without namespace) and I have only just now realised that it needs to be a regex in the line, not just a pattern, or a keyword. [Yes, I didn't read the fine print.] Can I suggest that for many others may not see the parameter field name aligning with the need for a regex expression (as in my grammar a pattern can just be a string).

If it does need to a regular expression, can we be more overt? Maybe even through in a wikilink to something to help on regex, or a warning that that line is not a simple alternative. Even something like having some drop downs at both ends of the title field with .*(default), ^, $ and (nothingness) that could at least make things obvious and simpler for the neophytes who just drop in a keyword. Thanks.  — billinghurst sDrewth 01:27, 24 July 2023 (UTC)Reply[reply]

Well, it's only sort of a regular expression. For the end user, treating it like a keyword is generally fine and should give the expected results. The flavour of regex used by Elastic Search isn't actually a full implementation. I.e. anchor operators like ^ and $ will not work. So if you searched for "foobar" expecting to get titles that are exactly or contain the word "foobar", simply putting in "foobar" works (though it is case-sensitive; I'm not certain if we have control over that).
Anyway I definitely agree we should link to the docs or something, especially since this is not the same regex engine many of us are used to -- PCRE/PRCE2 as is used by PHP (i.e. AbuseFilter), or the similar JavaScript regex syntax.
I will add a link and maybe change the field from "pattern" to "regular expression", for further clarity. Thanks for the suggestion! MusikAnimal talk 17:51, 24 July 2023 (UTC)Reply[reply]

Error with Mediaviews Analysis (on Wikimedia Commons)?[edit]

Hi there! I hope you are doing well. I noticed that you are one of the three programmers that developed the Pageview Analysis tool. So recently Mediaviews Analysis on Wikimedia Commons keeps showing the error message: "Error querying Media requests API - Not Found" for several old files (files uploaded > 1 day). Is there any ongoing improvement to this tool? Thanks. Đại Việt quốc (talk) 13:20, 3 October 2023 (UTC)Reply[reply]

@Đại Việt quốc It's likely the same as phab:T347899 which is an issue upstream with the pageviews API. Does the file names have parentheses, spaces, or a dash in them? If so, that's the issue. Hopefully it'll be fixed soon. MusikAnimal talk 05:07, 4 October 2023 (UTC)Reply[reply]
Hi! Thanks for replying. So the filename has parentheses and diacritics in them, spaces were fine though. This never happened before, was there any modifications done to the code of the tool? Đại Việt quốc (talk) 01:01, 13 October 2023 (UTC)Reply[reply]
There have been no recent updates to Mediaviews, no. If you're saying this worked before, it sounds like a regression in the pageviews API. At any rate, the right people are now aware of it so it should be fixed in due time. MusikAnimal talk 19:18, 16 October 2023 (UTC)Reply[reply]