[14:08:19] i am unable to access toolforge.org, iabot.toolforge.org also, is this known issue? [14:08:49] both seem to be working for me [14:09:15] both work here [14:10:54] work for me too [14:11:49] ok, i will clear cookies, etc and i will check [14:15:44] iabot has error 502 now (re @wmtelegram_bot: i am unable to access toolforge.org, iabot.toolforge.org also, is this known issue?) [14:16:20] OK now 503, so probably there is a i++ 😂 or maybe someone is working on it now [14:30:43] bozzy, when you say toolforge.org are you talking about accessing it via a browser or ssh? [14:35:50] hello again, few min back, i reported non access of *.toolforge.org [14:36:14] bozzy, when you say toolforge.org are you talking about accessing it via a browser or ssh? [14:36:28] apparently, few website status checkers are showing mixed reports. [14:36:37] i am using web browser [14:36:50] I mean HTTP status codes (re @wmtelegram_bot: bozzy, when you say toolforge.org are you talking about accessing it via a browser or ssh?) [14:37:45] i am using web browser.... [14:37:50] Guest8380: can you be more specific than 'inaccessible'? what exact errors are you getting? [14:40:05] search resukts showed restarting debice, cl cache, etc. i tried all of them. error: net::ERR_ADDRESS_UNREACHABLE [14:40:25] I can reproduce with curl https://iabot.toolforge.org. My traceroute enters in gw-wikimedia.init7.net, ae1-403.cr2-esams.wikimedia.org, xe-4-1-3.cr2-eqiad.wikimedia.org, and instance-tools-proxy-06.tools.wmflabs.org [14:42:18] I've just a timeout now [14:45:13] i am having issue since yesterday or before that, i have asked here before... [14:45:45] i am eng wikipedia w/username jindam vani [14:53:13] "curl https://iabot.toolforge.org" returns 200 on my laptop [14:53:59] iabot.toolforge.org resolves to 185.15.56.11 from here [14:54:11] if they return, please link them to https://wikitech-static.wikimedia.org/wiki/Reporting_a_connectivity_issue [14:55:08] could leave a user talk message. I would later, have to run now (re @wmtelegram_bot: if they return, please link them to https://wikitech-static.wikimedia.org/wiki/Reporting_a_connectivity_issue) [14:56:43] there's a chance that we caught them with that UA block last week [15:05:55] I don't know if you have changed something but now it works (and in my traceroute, after xe-4, I reach cloudgw1002) (re @bozzy: I can reproduce with curl https://iabot.toolforge.org. My traceroute enters in gw-wikimedia.init7.net, ae1-403.cr2-esams.wikimed...) [18:34:11] bd808: random style question -- I see this line in your code [18:34:13] if tool not in ('.well-known', 'index.php', 'robots.txt'): [18:34:16] which I would've written [18:34:26] if tool not in ['.well-known', 'index.php', 'robots.txt']: [18:34:38] Is a tuple more memory-efficient or otherwise better there? [18:36:18] (oops, I keep forgetting that you're at a conf) [19:46:02] andrewbogott: I don’t think it honestly makes enough difference to matter. [19:46:23] That's what I figured, was just curious :) [19:47:01] I'm now trying to add unique daily views to that tool and realizing that that only really works if the script always runs at midnight exactly :/ [20:25:21] Can I get a Phab admin to block https://phabricator.wikimedia.org/p/Katrinarowley0/ [20:25:37] They're screwing around with our workboard. VANDALISM [20:25:41] !help [20:25:41] If you don't get a response in 15-30 minutes, please create a phabricator task -- https://phabricator.wikimedia.org/maniphest/task/edit/form/1/?projects=wmcs-kanban [20:30:28] RhinosF1: thank you. :-) [20:35:25] Cyberpower678: np, saw it in my email [20:35:30] thanks for the cleanup [20:36:12] Cyberpower678: would you like phab-ban tool [20:36:17] Thank you actually. Harej and I were actively addressing workboard tickets, when they literally started fudging with the tickets we were working on. Lol [20:36:36] RhinosF1: Sure. I wouldn't mind having a ban hammer. [20:37:13] This particular user was specifically targeting our Workboard it seems. Seems like our "fans" found a new venue to play in. [20:37:47] Cyberpower678: done [20:37:59] Nice. [20:38:24] RhinosF1: how/where do I use it? [20:38:56] Cyberpower678: phab-ban.toolforge.org [20:39:00] bd808: sal is dead [20:39:25] fyi https://wikitech.wikimedia.org/w/index.php?title=Release_Engineering/SAL&diff=2011664&oldid=2011375 [20:39:42] Seems simple enough to use. [20:40:04] it is [20:40:13] enter username, press whack, profit [20:40:14] Any reason why it needs to be a tool vs just ungreying the disable user button? [20:40:31] phab acl is stupid [20:40:37] Oh. [20:40:38] it actually does the ban via a bot [20:40:43] Oh [20:41:08] Ah https://phabricator.wikimedia.org/p/PhabBanBot/ [20:41:15] yyes [20:41:18] example https://phabricator.wikimedia.org/people/manage/34328/#12458 [20:41:22] Cool. I'll need to bookmark the tool. [20:41:50] Can the tool also enable a user? [20:41:53] no [20:41:57] it is one way [20:42:12] Ah, so be careful who you whack then. [20:42:20] yes [20:43:22] Thanks for the acces.. [20:43:25] *access. [20:44:21] np [21:01:53] Well technically it would be as simple as updating the “Can Disable Users” policy on https://phabricator.wikimedia.org/applications/view/PhabricatorPeopleApplication/ [21:11:04] 14:34:38 <@andrewbogott> Is a tuple more memory-efficient or otherwise better there? <-- it used to be more efficient but AIUI in modern versions, Python is smart enough to see the list is hardcoded/never manipulated and pretends its a tuple [21:11:19] legoktm: makes sense, thanks! [21:31:07] andrewbogott: if you have access, can you restart tool-sal's webservice. [21:32:06] RhinosF1: did that help? [21:32:41] andrewbogott: yes, perfect! [21:34:21] thank you! [21:36:26] phab-ban should perhaps tell you you're not authorized before requesting a ban [21:38:48] Platonides: that does sound like a good improvement. Can you make a phab task for it and assume it to me. [21:39:03] *assign [21:45:50] bd808: sure [21:49:25] done: T317584 [21:49:25] T317584: phab-ban should tell you you're not authorized before requesting a ban - https://phabricator.wikimedia.org/T317584