[01:40:43] <wm-bot>	 !log anticomposite@tools-bastion-13 tools.stewardbots deploy 01aace0
[01:40:46] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[19:10:21] <wm-bot>	 !log jeanfred@tools-sgebastion-10 tools.integraality Deploy 5a91a78, 864d518, c9b199 (T251008), 0dd731f
[19:10:24] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.integraality/SAL
[19:25:28] <wm-bot>	 !log anticomposite@tools-bastion-13 tools.stewardbots SULWatcher/manage.sh restart # SULWatchers disconnected
[19:25:30] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stewardbots/SAL
[22:29:35] <wm-bot>	 !log bd808@tools-bastion-12 tools.gitlab-webhooks Built new image from 899024e8
[22:29:37] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gitlab-webhooks/SAL
[22:29:56] <wm-bot>	 !log bd808@tools-bastion-12 tools.gitlab-webhooks Restarted to pick up new image
[22:29:57] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.gitlab-webhooks/SAL
[22:46:04] <wm-bb>	 <sohom_datta> Is there a way to look at the source code of the `toolforge` tool ?
[22:47:24] <wm-bb>	 <sohom_datta> (Context: `toolforge jobs logs -f <jobname>` kills itself after a while and I wanted to debug/look at the code to understand why that happens)
[22:47:53] <wm-bb>	 <sohom_datta> (I'm not sure if it is something I'm doing v/s something that is wrong with the CLI)
[22:59:52] <bd808>	 @sohom_datta: there are a couple of parts. https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-cli (frontend) and https://gitlab.wikimedia.org/repos/cloud/toolforge/jobs-api (backend).
[23:00:53] <bd808>	 I have so far found that for myself direct use of `kubectl logs -f <pod>` is more stable that the `toolforge jobs logs` or `webservice logs` wrappers.