[12:03:47] Unfortunately, I didn't sign up. Can anyone jump in? (re @jhsoby: Hi folks, just a reminder that this will happen in approximately 3.5 hours (12:00 UTC). Hope to see many of you there!) [12:05:34] Never mind, wrong date! [19:40:02] Was there some change that prevents API login via normal password (not bot password) since December? [19:47:02] I thought that had been off for a while [19:54:57] potentially February 14 after 1200 UTC [19:55:25] and before 1800 UTC [19:59:33] hmm, though no, that is probably some grid deprecation thing or something, so it is a separate problem [19:59:48] hmm [20:01:54] yeah, as in cronfile is now empty, meh. [20:03:19] what is the current correct way to run a PHP CLI script on Toolforge? [20:03:50] I used to have [20:03:51] [20:03:52] > jstart -N nameofthejob -mem 500m php /path/file.php [20:06:51] toolforge jobs: https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#Use_case_continuity [20:07:18] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Jobs_framework#Grid_Engine_migration [20:08:09] `toolforge jobs images` for the available images (you probably want either `php7.4` or `php8.2`) [20:11:13] thanks! (I want 5.6 in this case, but 7.4 will do :) ) [20:16:31] what would be the equivalent of 0 */6 * * * ? (re @lucaswerkmeister: toolforge jobs: https://wikitech.wikimedia.org/wiki/News/Toolforge_Grid_Engine_deprecation#Use_case_continuity) [20:17:09] `--schedule '0 */6 * * *` should work, I think https://wikitech.wikimedia.org/wiki/Help:Toolforge/Jobs_framework#Creating_scheduled_jobs_(cron_jobs) [20:17:19] (strange that there’s no example of that in the table I linked earlier) [20:17:45] @lucaswerkmeister: you have toolforge root right? [20:17:50] yes [20:18:01] Can you restart stashbot [20:18:07] It's broken and failing to log [20:18:16] Including yours in -cloud a few minutes ago [20:18:32] Well half an hour ago [20:18:38] Plus many in -operations since [20:18:43] looking [20:18:51] nothing useful in its kubectl logs, meh [20:18:55] someone else will have to investigate that I think [20:19:31] ah, i didn’t notice that (re @wmtelegram_bot: Including yours in -cloud a few minutes ago) [20:19:49] I just saw in the telegram channel list that there was *some* message from but not that it was an error ^^ [20:19:58] heh [20:20:06] (if it hadn’t written anything at all I *think* I’d have noticed that there was only one unread message instead of two ^^) [20:20:42] anyway, I restarted it, though it hasn’t picked up its own restart log message (yet?) [20:20:46] let me try relogging the lexeme-forms [20:20:53] ah, nevermind [20:21:03] It looks fine now [20:21:38] yay [20:22:48] stashbot’s stashbot.log has a bunch of read timeouts for wikitech.wikimedia.org, whatever that means [20:25:46] wikitech seemed fine when I checked [20:27:01] at least no error received, thanks :) (re @lucaswerkmeister: --schedule '0 */6 * * * should work, I think https://wikitech.wikimedia.org/wiki/Help:Toolforge/Jobs_framework#Creating_schedule...) [20:27:22] now back to figure out why my other bot fails to log in [20:29:48] tried to add one now (re @lucaswerkmeister: (strange that there’s no example of that in the table I linked earlier)) [20:35:32] thanks. the first link does contain the schedule parameter, but I was confused by @hourly as in my case it is every 6 hours :) [20:37:19] (in the meantime I've managed to obtain telegram ban for a couple of days for some reason, and now I cannot write in the Hackathon group I assume because of aggressive anti-spam enabled. (I wonder if the ban is actually because of writing in the group, as I haven't been contacting any people who might've reported me in the last weeks or so 🤷‍♂️)) [20:42:24] apparently it was the @hourly :( : https://tools-static.wmflabs.org/bridgebot/06cb96fa/file_57777.jpg [20:43:00] (I can’t find an option to allowlist you or anything, so I just hope the ban will wear off on its own, sorry) [20:43:58] it will in 4 days :) (well, bans are progressive, if this was my first Telegram ban then it would probably be for 1 day or so) [20:45:25] they say there should be a way to report that action as false positive, I assume right where you made that screenshot [20:45:35] I am not sure it will help with the ban itself though [20:47:51] I’ve done that and it shows a banner that I can manage the anti-spam settings in [elsewhere] [20:48:04] where I can indeed see that aggressive anti-spam is turned on – I’m not sure if it would be a good idea to turn it off [20:48:14] no idea if the report as false positive actually went through otherwise or not [20:49:19] the ban is still in place, so I guess either it is not reversible, or it takes some review. well, no big deal anyway. [20:52:23] as to potentially disabling anti-spam, well, we don't have it in Wikimedia General for example. I think Shieldy or whatever takes the job of filtering who is allowed instead (and manual moderation when it fails). The difference is thought that that group is not bridged to IRC, once stuff gets sent to IRC it cannot be removed there (obviously). So in a way this does call for a more preventative moderation. Now if there are indeed many [20:52:24] true positives it catches that I don't know, I guess you can investigate by reviewing the logs 🤷‍♂️ [21:02:51] hmm, the log in issue with my other bot has magically disappeared. my guess is that it was because I initially tried to log in into an incorrect account, so perhaps there was some sort of cooldown after that (even though after those incorrect attempts I manually logged in into my bot, but indeed even that went through from 2nd attempt I think) [21:04:49] this reminds me a recent meme I've seen https://usercontent.irccloud-cdn.com/file/IlW6CjFJ/image.png [23:52:06] In Hackathon 2023, the GWToolset was removed from everywhere. [23:52:28] In Hackathon 2024, will LiquidThreads be removed from everywhere? :) [23:59:30] Seriously. Where is it still used? It's still on translatewiki, but new pages are no longer created. Is it still seriously used on any Wikimedia wikis?