[00:00:03] zabe: I think maybe they merged so many tasks that it is taking phab a while to catch up with reporting? [00:00:22] * bd808 does not envy the cleanup on that crappy vandal action [00:01:15] musikanimal: do you still have that "undo all the crappy edits" script for phabricator? T298058 is a wreck. [00:01:15] T298058: [Impact Analysis] Evaluate Impact of Mobile Reply and New Discussion Tools - https://phabricator.wikimedia.org/T298058 [00:01:40] oh yeah they merged like 100+ tasks [00:02:47] I don't... but I thought there was an official rollback script now? https://phabricator.wikimedia.org/T198283 [00:03:28] https://gitlab.com/aklapper/phabricator-revert-user-actions [00:03:38] @lucaswerkmeister: I added both of your phab accounts to #acl*userdisable so that you can use https://phab-ban.toolforge.org/ in the future when you see a vandal to block [00:03:57] nice, thanks *bookmarks* [00:07:31] * bd808 pings a more powerful phab admin to see if they can cleanup [00:11:51] even better :) [00:19:04] I think it's all cleaned up now [00:19:27] thanks JJMC89 :) [00:20:11] :) [00:20:12] thanks you two :) [00:23:53] we should maybe bundle the rollback script into the phab-ban tool. Whoever can be trusted with banning surely can be trusted with rolling back, and often you want to do both [00:26:23] afaik it's only usable via command-line rightn ow [00:26:52] right, it'd have to be rewritten in Python. But that shouldn't be too hard, for someone good at Python (not me :) [00:28:06] or it could just call the shell script right on the Toolforge account but that feels wrong [00:28:17] the advantage of the CLI script is that it (supposedly) can delete the vandalism so it doesn't keep the polluted task history [00:29:32] and by CLI script, I'm referring to https://wikitech.wikimedia.org/wiki/Phabricator#Revert_all_activity_of_a_given_user which requires root on the phab host itself basically [00:29:54] I see, because it has database access [00:32:50] checked aphlict1001 (the realtime notification server part of phab that is a separate VM) and appears fine. because the other day it ran out of disk due to a huge log.. and saw backlog about all the notification processing [00:33:02] lgtm though [01:29:35] legoktm: I think I have things working. I'll need to touch the container to see if the updater is right, but thanks for the pointers. https://phabricator.wikimedia.org/T297800#7582151 has most of what I did. [01:30:22] nice! [01:30:31] did you need "docker-compose" installed for something else? [01:33:57] no, I turned out not to need it. I forgot that this one is a single container. Toolhub's setup used docker-compose to manage a group of things which I think is why my brain added it. [01:34:36] * bd808 may try switching the toolhub demo server to podman later this week [01:48:45] gotcha [01:49:01] I use podman locally so now being able to use it on VPS is really nice [10:39:00] !log admin dropped egress NAT exceptions for WMF apt repos, T298042 [10:39:04] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL [10:39:05] T298042: evaluate & drop cloud NAT exceptions for APT repositories - https://phabricator.wikimedia.org/T298042 [11:06:13] !log toolsbeta bump quotas, instances from 50 to 55, CPU from 100 to 150, RAM from 200GB to 250GB (T277653) [11:06:17] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [11:06:19] T277653: Toolforge: add Debian Buster to the grid and eliminate Debian Stretch - https://phabricator.wikimedia.org/T277653 [11:26:24] Prygelnde Maskengegner? https://www.presseportal.de/blaulicht/pm/30127/5104285 [11:27:36] oops! wrong channel sorry [11:48:42] !log toolsbeta Joining grid node toolsbeta-sgewebgen-10-2.toolsbeta.eqiad1.wikimedia.cloud to the toolsbeta cluster - cookbook ran by arturo@endurance [11:48:45] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:03:46] !log toolsbeta Joining grid node toolsbeta-sgewebgen-10-2.toolsbeta.eqiad1.wikimedia.cloud to the toolsbeta cluster - cookbook ran by arturo@endurance [12:03:48] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:03:52] !log toolsbeta Node toolsbeta-sgewebgen-10-2.toolsbeta.eqiad1.wikimedia.cloud joined the grid cluster toolsbeta. - cookbook ran by arturo@endurance [12:03:54] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:04:07] !log toolsbeta Joining grid node toolsbeta-sgewebgen-10-3.toolsbeta.eqiad1.wikimedia.cloud to the toolsbeta cluster - cookbook ran by arturo@endurance [12:04:09] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:04:12] !log toolsbeta Node toolsbeta-sgewebgen-10-3.toolsbeta.eqiad1.wikimedia.cloud joined the grid cluster toolsbeta. - cookbook ran by arturo@endurance [12:04:13] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:07:26] !log toolsbeta Joining grid node toolsbeta-sgewebgen-10-3.toolsbeta.eqiad1.wikimedia.cloud to the toolsbeta cluster - cookbook ran by arturo@endurance [12:07:28] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [12:50:51] !log toolsbeta Joining grid node toolsbeta-sgewebgen-10-3.toolsbeta.eqiad1.wikimedia.cloud to the toolsbeta cluster - cookbook ran by arturo@endurance [12:50:53] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [16:24:09] !log toolsbeta Joining grid node toolsbeta-sgewebgen-10-3.toolsbeta.eqiad1.wikimedia.cloud to the toolsbeta cluster - cookbook ran by arturo@endurance [16:24:11] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [16:24:15] !log toolsbeta Node toolsbeta-sgewebgen-10-3.toolsbeta.eqiad1.wikimedia.cloud joined the grid cluster toolsbeta. - cookbook ran by arturo@endurance [16:24:16] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [16:32:01] !log toolsbeta removing instance toolsbeta-sgewebgen-10-2 - cookbook ran by arturo@endurance [16:32:04] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Toolsbeta/SAL [18:02:24] Suddenly getting a HTTP 403 on SPARQL requests from PAWS today. Can someone shed some light on that? [18:06:11] Infrastruktur: what SPARQL endpoint are you getting 403 responses from? [18:08:36] https://query.wikidata.org/sparql. I was able to run a query from home using WikibaseCLI though. [18:14:48] weird. The #wikimedia-search channel might be a good place to ask if there is any known problems with the main WDQS. I haven't heard anything recently about intentional maintenance or restrictions [18:16:54] Infrastruktur: are you setting a proper user agent? [18:17:07] I believe the default Python requests user agent has been banned from WDQS for a long time [18:18:54] No I don't think so, I'm using SPARQLWrapper. I will try and see. [18:26:58] That fixed it. Thank you Lucas. [18:27:09] yay :) [20:10:45] [Q] I have a list of 100 URLs to articles in Wikipedia English. I want to know which of those articles contain the word "banana". Is there any tool that could help me doing this? [20:14:36] Petscan will work for that I beleive. https://petscan.wmflabs.org/ [20:16:24] Article names go in 'Other sources/Manual list' and for 'Other sources/Search' use 'insource:banana' [21:20:08] Thanks! [23:17:13] I suspect the wikibugs 'pull' thingy isn't working. [23:17:17] https://gerrit.wikimedia.org/r/c/labs/tools/wikibugs2/+/749279 [23:17:32] pull.php serves a blank page, is that the expected result? The change does not appear to have been applied. [23:18:06] docs suggest deployment is now done by bot operators via shell - https://www.mediawiki.org/wiki/Wikibugs [23:35:47] channel list changes are supposed to be auto-deployed [23:35:53] but the last few times it definitely didn't work