[00:06:33] kanashimi: you can ssh into a Toolforge bastion, become your tool, and then use `webservice node18 shell` to get an interactive shell inside a 'node18' container and poke around. You can replace the 'node18' there with any `webservice` supported image (see ` webservice --help`). [00:08:48] Thank you. I'm changing to curl. `webservice node18 shell` throws an error. [00:08:49] Error from server (Forbidden): pods "shell-1751328455" is forbidden: exceeded quota: tool-toc, requested: requests.cpu=125m, used: requests.cpu=4, limited: requests.cpu=4 [00:10:45] That toc tool has 8 containers running that have used up all of the tool's default quota. [00:11:40] You can ask for more quota at https://phabricator.wikimedia.org/project/view/4834/ [00:55:17] Thank you [12:45:22] Hi. I am testing the new push to deploy workflow and I need the buildpack with the -L flag (https://github.com/DaxServer/wikibots). From the docs (https://wikitech.wikimedia.org/wiki/Help:Toolforge/Deploy_your_tool), I was not able to figure out what the parameter for the latest flag should be in the toolconfig yml. Is it supported yet? [12:50:42] DaxServer: that's not yet supported, but soon! https://gitlab.wikimedia.org/repos/cloud/toolforge/components-api/-/merge_requests/72 [12:50:58] let me add that also to the docs [12:51:59] Cool thanks! [14:01:48] !log soda@tools-bastion-13 tools.yapping-sodium soda built and uploaded a new version [14:01:50] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.yapping-sodium/SAL [15:19:39] Does anyone know how to make the alt attribute be shown on mobile devices? [15:19:39] In this page (https://br.wikimedia.org/wiki/WikiCon_Brasil_2025/Cabe%C3%A7alho), for example, all the images have alt attributes (the focus is on the logo), that desktops and laptops screen readers can read. Bit if you try to read on mobile, the screen reader reads the thumbnail filename, like 500px... [15:21:02] how is this relevant to wikimedia cloud services? [15:25:27] not relevant. but I did test with mdot and desktop site both using the built in "Talkback" Android screenreader and it's fine. (re @wmtelegram_bot: how is this relevant to wikimedia cloud services?) [15:54:15] !log soda@tools-bastion-13 tools.yapping-sodium soda built and uploaded a new version [15:54:18] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.yapping-sodium/SAL [17:09:13] Getting [17:09:13] pod tool-superyetkin/shell-1751389212 terminated (OOMKilled) [17:09:15] error when running a memory intensive PHP script [17:11:34] can you say quantitatively how intensive? (re @Yetkin: Getting [17:11:36] pod tool-superyetkin/shell-1751389212 terminated (OOMKilled) [17:11:37] error when running a memory intensive PHP script) [17:11:41] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Kubernetes#Container_memory_limits [17:14:56] about 1G, I guess [17:21:55] Running the script as [17:21:57] php cron_pageviews.php --mem 1000m [17:21:58] after webservice shell. Do I need to do something else? [17:25:16] @Yetkin: See https://wikitech.wikimedia.org/wiki/Help:Toolforge/Web#Runtime_and_cpu_memory_limits for a bit of description on the --cpu and --mem flags that you can use to raise the limits for your Pod when you run the `webservice shell` command. [17:26:10] You will need the Pod to have higher limits to get past the OOM killer [17:27:31] The defaults are 0.5 CPU and 512M of ram. [17:29:45] `kubectl describe quota` will show you how much of your total quota is bineg used by jobs you are already running. You can make a single Pod as big as `--cpu 3 --mem 6Gi` if you have space in your active quota [22:18:41] All Flickr tools should add license Nr 11 and 12 to their list of approved licenses, now that the website has implemented support for 4.0 Creative Commons licenses [22:19:02] Would be cool if flickr2commons.toolforge.org could still get an update [23:58:12] @IVeertje: https://bitbucket.org/magnusmanske/flickr2commons/issues is the bug tracker for flickr2commons. Magnus does not monitor this channel.