rig/changelog.d/133.md at 1daf7004d7a0a0f47666b07c2bc086a563a9551e

cluade-reviewer-andresmgsl 1daf7004d7 fix(forgejo-runner): 'active' is not proof the runner is fetching

status reports `systemctl is-active` as the service line, and that is the
strongest health signal it has — the command reads only on-disk config, by
contract. But a poller can go quiet while the process stays up: measured
2026-07-30 while probing for #129, a daemon logged "[poller] launched" and
never fetched a job dispatched four minutes later, while a daemon started
fresh claimed that same queued task in one second. Both times it read as a
label-mapping bug on the forge, which is the wrong place to look.

Says so where an operator already looks when nothing is obviously wrong, and
names the remedy. log, not warn: an idle-but-healthy runner is silent in
exactly the same way a stalled one is, so there is no signal separating them
and a warning on every run would be crying wolf.

No network call and no token read — the header contract, and test/cli.sh's
existing guard, both stand.

Refs #133

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-31 00:15:02 +00:00

129 B

Raw Blame History

Fixed

rig forgejo-runner status no longer lets a service's (active) stand as proof the runner is fetching jobs (#133)

129 B Raw Blame History

Fixed

129 B

Raw Blame History