garm/runner/pool
Gabriel Adrian Samfira 80e08e7db0 Fix max runners check and leaky JIT runners
The check for max runners was added to CreateInstance(), but we crete the
JIT runners before we run the function to add a runner to the DB. The defer
function to clean up the JIT runner was being run after the error return
generated by CreateInstance. So the cleanup code never ran. Additionally
we would know that max runners was reached only after creating the JIT
runner. Which kills rate limits.

Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
2026-02-11 23:06:15 +02:00
..
cache.go Attempt to use the scalset API and caching 2025-08-24 22:36:44 +00:00
common.go Attempt to use the scalset API and caching 2025-08-24 22:36:44 +00:00
pool.go Fix max runners check and leaky JIT runners 2026-02-11 23:06:15 +02:00
stub_client.go Ensure scale set exists 2025-08-23 18:55:08 +00:00
util.go Cache jobs in pool manager 2025-10-05 00:49:41 +03:00
util_test.go Add copyright header 2025-05-20 09:43:29 +00:00
watcher.go Cache jobs in pool manager 2025-10-05 00:49:41 +03:00