[01:59:17] taavi: Is there a sensible way to import existing cloudvps_web_proxy resources into terraform state? Looking at the code, I see it's trying to import by ID (https://gitlab.wikimedia.org/repos/cloud/cloud-vps/terraform-cloudvps/-/blob/main/internal/provider/proxy_resource.go#L347) but I can't find the ID anywhere to use. [09:05:04] I announced my Tool sweep proposal on the mailing list, https://lists.wikimedia.org/hyperkitty/list/cloud@lists.wikimedia.org/message/4MAN77NS47TRANE3DK375VL3W3XGY4CT/ [09:05:12] (https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Tool_sweep) [12:14:24] You should include why you want to do this. (re @wmtelegram_bot: (https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Tool_sweep)) [15:47:59] I like the tools sweep idea, but in my opinion the main problem are the dead tools, tools that don't work for years, lack of licence or public source are minor issues compared to that [16:23:49] an easy way to make a list to start the tools triage is creating a script that reads the time of last command in the .bash_history of each tool, the tools with oldest time are not maintained for many years [16:26:13] I am curious to know how many of the 3200+ tools have no command in bash_history for more than 5 years [17:38:10] Hello - I’m interested in hosting copies of the XML dump files…..I’ve reached out via email address and mailing list but haven’t received a response [17:38:32] wondering if that’s something still needed?  If so, can anyone point me in the right direction for next steps? [17:42:10] Why leave so quickly? [17:42:43] RyanM: which email and mailing list did you use? [17:44:45] RhinosF1 mailing list: xmldatadumps-l@lists.Wikimedia.org. Email: ops-dumps@wikimedia.org (from the Mirroring Wikimedia project XML dumps page) [17:45:29] RyanM: ok, I'll poke the dump team. Please try and stay connected. It might take a bit to respond. [17:45:58] RhinosF1 thanks for your help! [18:06:40] RyanM: I suspect the answer is "because it's Christmas" [18:07:09] At least for the mailing list... It's currently a WMF holiday [18:07:30] You don't state when you emailed the other address [18:10:00] Reedy I did consider the holidays might be part of the reason….I emailed the mailing list this week; however, I emailed the ops-dumps address before the holidays [18:10:16] Before the holidays? A day? A week? A month? [18:10:34] Last week before Christmas is the worst! 😊 [18:13:56] Reedy I just cheeked - it was the 21…..still possible the holidays are the likely culprit:)  but thought I’d try another avenue in case the 2 I tried weren’t “active” any longer [18:14:27] Yeah... Depending on TZ, that's maybe 2 or 3 working days "before christmas" [18:14:58] You should get a reply in the new year... I think there's only one or two people that maintain that ops-dumps email [18:16:23] sounds great, I’ll wait to hopefully hear something next week once folks are back from the holidays…..appreciate the help! [18:18:32] 21st is way too late. My work was send it by the end of the 14th or tough if you want it before the 3rd [18:41:22] stw: not at the moment, but it's on my (never-ending) todo list [22:48:26] @MaartenDammers: added a section, will reply on-list with some more detail [22:48:36] danilo: ooh, that's a great idea [22:53:31] legoktm: I made the research, 19% of tools have .bash_history older than 5 years and 10% have no .bash_history, I added more details in the tool sweep talk page [22:56:11] I was just looking through the list :D [22:56:56] interestingly it correctly flagged "libraryupgrader", which is one of my tools. I only created the tool to be used for email forwarding but apparently never even bothered to log in [22:59:07] I wonder why "become" was created [23:02:45] !log linkwatcher `samtar@coibot:/home/billinghurst$ sudo rm syslog.script` for T326014 [23:02:48] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Linkwatcher/SAL [23:02:48] T326014: coibot.linkwatcher out of disk space - https://phabricator.wikimedia.org/T326014 [23:03:17] it's possible that in some cases the maintainer didn't log in (frequently) as the user [23:03:39] e.g. just transferring new files to the folder [23:03:52] but it's a good first filter, indeed [23:04:10] there's a tool named "scfc-test-can-be-deleted-anytime" [23:05:45] hehe [23:06:29] another metric could be to start by the most used tools [23:06:33] (or the less used...) [23:07:13] !log tools.scfc-test-can-be-deleted-anytime Marked for deletion in 40 days [23:07:14] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.scfc-test-can-be-deleted-anytime/SAL [23:07:58] I personally thought of doing a random order just so you'd get a mix of good tools and bad tools, and it wouldn't be all so depressing [23:08:13] but starting with the unused ones seems like some easy wins! [23:08:19] seemingly* unused