[04:17:46] <derenrich>	 "ssh login.toolforge.org" -> "Connection closed by 185.15.56.62 port 22" again
[07:10:41] <taavi>	 !log tools kill bunch of unwanted processes off of tools-bastion-13 T393732, please run your things as jobs
[07:10:45] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[07:10:45] <stashbot>	 T393732: Toolforge bastion sssd/LDAP flakiness (May 2025) - https://phabricator.wikimedia.org/T393732
[08:47:36] <taavi>	 !log metricsinfra failing over grafana to grafana-2 T393735
[08:47:38] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Metricsinfra/SAL
[08:47:38] <stashbot>	 T393735: Upgrade metricsinfra Grafana hosts (grafana.wmcloud.org) to Bookworm / Grafana v11 - https://phabricator.wikimedia.org/T393735
[09:06:11] <arturo>	 !log wikilink bump object storage quota, with: `aborrero@cloudcontrol1006:~$ sudo radosgw-admin quota set --quota-scope=user --uid wikilink\$wikilink --max-size=15GB --max-objects=20000` (T392870)
[09:06:14] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Wikilink/SAL
[09:06:14] <stashbot>	 T392870: Request to increase object storage capacity - Wikilink project - https://phabricator.wikimedia.org/T392870
[09:46:54] <stw>	 tyvm for the merge taavi :)
[12:20:34] <wm-bb>	 <nokibsarkar> Same issue with me (re @arcstur: Hi guys, can't become any tool. It is warning me that sudo requires a password. What can I do?)
[12:21:22] <wm-bb>	 <nokibsarkar> I cannot `become` any of my tool
[12:23:37] <arturo>	 ok
[12:23:42] <arturo>	 we are evaluating rebooting the system
[12:24:04] <arturo>	 meanwhile you can use dev.toolforge.org
[12:25:58] <wm-bb>	 <nokibsarkar> ok. dev is working
[12:27:40] <wm-bb>	 <nokibsarkar> is there any nodejs version 22 available on toolforge? I would like to host my nextjs tool
[12:29:09] <arturo>	 !log tools hard-reboot tools-bastion-12 (login.toolforge.org) because unresponsive (out of memory)
[12:29:13] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[12:31:33] <arturo>	 !log tools hard-reboot tools-bastion-13 (login.toolforge.org) because unresponsive (out of memory) -- previous reboot was for tools-bastion-12 (dev.t.o) by mistake
[12:31:35] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[13:22:27] <dhinus>	 @nokibsarkar I'm not sure what's the latest node.js version available, and I'm struggling to find where that's defined, does anybody remember how to find the version of the node buildpack?
[13:47:32] <dhinus>	 @nokibsarkar looks like we currently support Node.JS v20 but not yet v22. you can follow T380127 to know when newer versions will be available (hopefully soon!)
[13:47:33] <stashbot>	 T380127: [builds-builder] Add support for Heroku's "24" builder stack based on Ubuntu 2024.04 noble - https://phabricator.wikimedia.org/T380127
[14:04:44] <wm-bb>	 <lucaswerkmeister> dhinus: https://wikitech.wikimedia.org/wiki/Template:Toolforge_latest_image#Runtimes has versions for non-buildpack at least
[14:07:27] <dhinus>	 lucaswerkmeister: thanks! that's for toolforge-* docker images though, I was looking for versions supported by the toolforge build service
[14:08:14] <dhinus>	 I ended up running "pack build test-app --path . --builder tools-harbor.wmcloud.org/toolforge/heroku-builder:22"
[14:09:35] * dhinus realizes he replied without reading the end of the sentence ("for non-buildpacks at least") :P
[14:12:07] <wm-bb>	 <lucaswerkmeister> :P
[14:12:27] <wm-bb>	 <lucaswerkmeister> to be fair I was also thinking of digging up that link and sending it before I’d read the end of your message ^^
[14:14:18] <dhinus>	 :D
[14:16:41] <wm-bb>	 <lucaswerkmeister> (also it feels like this is information we should have available on toolforge somewhere™ as more and more tools are encouraged to move to the build service)
[14:17:12] <wm-bb>	 <lucaswerkmeister> https://wikitech.wikimedia.org/wiki/Help:Toolforge/Building_container_images#Supported_languages has a list of languages but without versions
[14:18:37] <dhinus>	 yep it should be possible to expose that information somewhere, it might be worth filing a phab task
[14:20:35] <dhinus>	 the tricky part is that it depends on the upstream heroku buildpacks, and we should be able to expose the version of the buildpack we are using, but which Node.js version is supported by version X of the buildpack is probably harder
[14:21:19] <wm-bb>	 <lucaswerkmeister> yeah
[14:25:58] <wm-bb>	 <lucaswerkmeister> I was thinking the versions could “just” be determined and updated manually each time we update the buildpack version, which is presumably not super common
[14:26:09] <wm-bb>	 <lucaswerkmeister> but of course “we” here really means “you” and so that’s easy for me to say :P
[14:26:26] <wm-bb>	 <lucaswerkmeister> (s/common/frequent/ is probably a better word above)
[14:31:48] <dhinus>	 yeah I agree that manually updating could be good enough, though if we add a --latest option the max version will change without any action on our side (I think) -- see https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-cli/-/merge_requests/103
[14:33:29] <dhinus>	 or maybe we still need to import the buildpack to make it available in toolforge? in any case, I agree we should have a list of versions somewhere, even if not perfectly up to date
[14:34:49] <dhinus>	 yes we're still publishing the "latest" version to our registry, so we control when that changes: https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-api/-/merge_requests/124/diffs
[14:35:13] <wm-bb>	 <lucaswerkmeister> good, I was surprised at the implication there for a moment ^^
[14:36:05] <dhinus>	 I kinda liked the idea of having a switch to say "just fetch the latest from upstream", but the way it's implemented is probably way safer :)
[14:36:26] <wm-bb>	 <lucaswerkmeister> yeah :)
[14:37:13] <dhinus>	 I'll create a phab task if you're not already creating one
[14:40:33] <wm-bb>	 <lucaswerkmeister> I’m not so far
[14:40:34] <wm-bb>	 <lucaswerkmeister> thanks!
[14:45:55] <dhinus>	 T393789
[14:45:55] <stashbot>	 T393789: [build-service] We should document which versions of Node.js, PHP, Go, etc. are supported - https://phabricator.wikimedia.org/T393789
[14:46:01] <dhinus>	 feel free to improve the description
[18:01:03] <wm-bot>	 !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed c26a336aa8 (better viewport units for mobile, hopefully)
[18:01:05] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL
[19:44:06] <wm-bot>	 !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed b8820a19ce (eslint improvements)
[19:44:08] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL
[20:33:01] <wm-bot>	 !log lucaswerkmeister@tools-bastion-13 tools.wdactle deployed 97b7de4ece (improved victory message)
[20:33:03] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.wdactle/SAL
[22:10:22] <wm-bot>	 !log bd808@tools-bastion-12 tools.gitlab-content Built container from 8601a403
[22:10:23] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gitlab-content/SAL
[22:10:52] <wm-bot>	 !log bd808@tools-bastion-12 tools.gitlab-content Deployed container built from8601a403
[22:10:53] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gitlab-content/SAL