[12:08:05] $ ssh dev.toolforge.org [12:08:06] Connection closed by 185.15.56.57 port 22 [12:08:08] Any incident or planned activity going on? [12:09:28] the normal bastion works for me fwiw [12:10:37] I can get into toolforge-dev as root – looks like SSSD is down [12:11:21] I’ll leave it alone for now, I don’t want to risk messing stuff up and I don’t think unbreaking toolforge-dev is urgent enough as long as the regular bastion still works [12:12:17] Did monitoring trigger some sort of incident or do we need a phab task? (re @lucaswerkmeister: I can get into toolforge-dev as root – looks like SSSD is down) [12:12:54] I don’t see anything in the recent new tasks… probably worth creating one, yeah [12:14:46] https://phabricator.wikimedia.org/T389717 (re @lucaswerkmeister: I don’t see anything in the recent new tasks… probably worth creating one, yeah) [12:17:24] thanks, commented [12:18:45] !status toolforge-dev down (T389717), no other known issues [12:18:45] T389717: dev.toolforge.org unreachable - https://phabricator.wikimedia.org/T389717 [12:19:24] (I’m assuming the “ingress issues” which were still in there (from 2025-03-05) were just outdated) [15:15:32] !status Ok [16:31:52] Our task got vandalized by https://phabricator.wikimedia.org/p/Stephonjeffries19/ . Does blocking them on MediaWiki.org prevent them from doing more edits on Phabricator? I recall something like that (re @wmtelegram_bot: T389717: dev.toolforge.org unreachable - https://phabricator.wikimedia.org/T389717) [16:45:06] Where / how I should inform ongoing vandalism in Phabricator?  Ie. somebody with blocking rights should check what https://phabricator.wikimedia.org/p/Stephonjeffries19/ is doing. [16:45:48] I just banned them via https://phab-ban.toolforge.org/, someone else will have to do the cleanup I’m afraid (I believe there are scripts for it but I don’t have the privileges to run them) [16:45:59] thanks [16:48:37] I added you two to the acl*userdisable group too, which controls access to the tool (it’s “viral”, just like trusted-contributors) [16:55:42] Hmm, just noticed that I'm a member since 2018. Now I know what tool to use 😊 (re @lucaswerkmeister: I added you two to the acl*userdisable group too, which controls access to the tool (it’s “viral”, just like trusted-contributor...) [17:31:59] yeah a lot of people on the list apparently never got told they got added to the list [18:35:17] How to initialize a Next.js project in Toolforge