[10:57:20] <lucaswerkmeister>	 !log tools.admin granted Reedy some more comprehensive access per https://wikitech.wikimedia.org/wiki/Portal:Toolforge/Admin/Toolforge_roots_and_Toolforge_admins (tools member in horizon, toollabs-trusted on Gerrit)
[10:57:22] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.admin/SAL
[10:57:28] <lucaswerkmeister>	 someone else will have to do repos/cloud/toolforge on GitLab because I don’t appear to be in it either
[10:57:44] <lucaswerkmeister>	 convenience link: https://gitlab.wikimedia.org/groups/repos/cloud/toolforge/-/group_members
[11:02:39] <taavi>	 done both
[11:09:08] <wm-bb>	 <lucaswerkmeister> yay thanks (I don't have access to my bouncer on my phone ^^)
[12:41:08] <LD>	  I'm using the Toolforge Build Service (Cloud Native Buildpacks, no Dockerfile) for the organon tool. Every toolforge build start (using github repo) seems to reinstall all Python dependencies from scratch, even when only application code changes (not requirements.txt/pyproject.toml). Is there a buildpack layer cache mechanism persisted between
[12:41:09] <LD>	 builds that I could enable/configure, or is this expected behavior (no cache retained between build invocations)? I'd like to avoid a full dependency reinstall when only the frontend build (web-app/dist) or Python code changes without touching dependency files.
[12:43:10] <Damianz>	 There is no caching currently, every build is essentially a clean container - it will use wheels etc but if things require compiling it can be a little slow sometimes
[12:51:28] <godog>	 !log toolschecker delete tool -- now unused
[12:51:29] <stashbot>	 godog: Unknown project "toolschecker"
[12:51:30] <stashbot>	 godog: Did you mean to say "tools.toolschecker" instead?
[12:51:37] <godog>	 !log tools.toolschecker delete tool -- now unused
[12:51:37] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.toolschecker/SAL
[12:57:49] <dcaro>	 LD, Damianz yep, there's no easy way to cache layers using buildpacks (that I know of, pip install might pull newer/different packages depending on when it's run). We were considering at some point adding a caching proxy for dependencies (apt/pip/go packages/etc..), that should speed up the build some, but the compilation parts would still be needed
[13:44:59] <andrewbogott>	 !log admin restarting designate services in eqiad1; seeing many miscellaneous designate-sink errors in logs
[13:45:02] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Admin/SAL
[15:00:17] <LD>	 thanks damianz & dcaro :)
[16:55:12] <dcaro>	 !log tools resize haproxy-7
[16:55:13] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[17:03:53] <dcaro>	 !status DOWN
[17:11:23] <dcaro>	 !log tools resize haproxy-8
[17:11:25] <dcaro>	 !status OK
[17:11:25] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL
[17:11:28] <bd808>	 dcaro: anything folks can help with? I spot checked some of my tools and they seem up?
[17:11:55] <bd808>	 dcaro: oh.. I see the OK now. Sorry for the noise
[17:12:04] <dcaro>	 bd808: just let me know if you see any failing ones yep, though from stats/etc it seems everything is back up again
[17:12:20] <dcaro>	 thanks btw :)
[20:06:33] <mutante>	 !log devtools puppetmaster-1003: /srv/git/operations/puppet# sudo -u gitpuppet git pull origin
[20:06:35] <stashbot>	 Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Devtools/SAL