[09:34:00] !log lucaswerkmeister@tools-bastion-13 tools.codex-playground deployed 9d842cfbe8 (Codex 1.20.1) but it’s not working [09:34:01] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.codex-playground/SAL [09:36:12] !log lucaswerkmeister@tools-bastion-13 tools.codex-playground deployed 6930ae89e9 (revert to Codex 1.19.1) [09:36:13] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.codex-playground/SAL [09:55:36] stupid question: is StrikerBot supposed to update GitLab toolforge-repos membership when tool maintainers are added? [09:56:04] https://gitlab.wikimedia.org/toolforge-repos/phpunit-results-cache/-/project_members only has Arthur as a direct member, even though he also added me to the tool and I subsequently added `tools.wmde-wd-team` [09:56:22] (I don’t know whether he created the gitlab repo before or after adding me; I certainly added `tools.wmde-wd-team` after the gitlab repo was created) [09:56:53] I was hoping all the `tools.wmde-wd-team` members would also get access to the repository, but I don’t know if I should file that as a feature request, or if it’s supposed to already be implemented and has a bug / regression :D [14:33:03] !log lucaswerkmeister@tools-bastion-13 tools.stashbot bin/stashbot.sh restart # quit with "Read error: Connection reset by peer" for no reason that I can see (nothing suspicious in kubectl logs) [14:33:05] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.stashbot/SAL [15:02:12] sounds like it’s a missing feature: T317376 (re @lucaswerkmeister: stupid question: is StrikerBot supposed to update GitLab toolforge-repos membership when tool maintainers are added?) [16:29:38] @lucaswerkmeister: in classic form, I shipped the MVP of Striker->gitlab integration and then moved on to other things. The two general problems needing a solution there are what algorithm to use to decide to add/remove a user on the gitlab side and when to trigger the change.