jason 0abc43bffc 🐛 Fix act_runner registration order 🐛 ...

Runners were launched in parallel subshells with only a 2-second gap
between them. act_runner register is a network call; if Gitea was
still warming up any registration could race past an earlier one,
causing Gitea to assign IDs out of sequence (1,3,2,5,4 instead of
1,2,3,4,5).
Split into two phases: register all runners sequentially first so IDs
are assigned in the correct order, then launch all daemons in parallel
once every runner is confirmed registered.
- rootfs/usr/local/bin/start-runners: split __start_runner into
__register_runner (sequential, phase 1) and __start_runner_daemon
(parallel, phase 2); remove the sleep 2 workaround

rootfs/usr/local/bin/start-runners

2026-05-24 21:37:50 -04:00

..

bin

🐛 Fix act_runner registration order 🐛

2026-05-24 21:37:50 -04:00

etc/docker

🐛 Fix silent download failure and cosmetic naming bugs 🐛

2026-05-24 19:58:15 -04:00

share/template-files

🔧 Sync template framework updates and fix app.ini config 🔧

2026-05-24 12:19:59 -04:00