An idle build machine's empty fetch is asked again, not read as the end (hq ADR 0190) #234

2026-10-03T09:41:37Z

mesh-admin commented

2026-10-03 09:41:37 +00:00

Found on the first live build agents, 2026-10-03: every idle agent exited clean every half minute and was restarted by its supervisor, with nothing in the log to say why. A fetch on a context without a deadline waits the client's own while and reports the deadline passed — the client's, not ours — and the loop read it as "stop". Now only our own context ending ends the machine; an empty fetch, however the client reports it, is asked again. go test ./internal/link/ green on a real bus.

Found on the first live build agents, 2026-10-03: every idle agent exited clean every half minute and was restarted by its supervisor, with nothing in the log to say why. A fetch on a context without a deadline waits the client's own while and reports the deadline passed — the client's, not ours — and the loop read it as "stop". Now only our own context ending ends the machine; an empty fetch, however the client reports it, is asked again. `go test ./internal/link/` green on a real bus.

mesh-admin added 1 commit 2026-10-03 09:41:38 +00:00

An idle build machine's empty fetch is asked again, not read as the end (hq ADR 0190) 59166b1031

A fetch on a context without a deadline waits the client's own while and reports the deadline
passed — the client's, not ours — and the loop read it as "stop": every idle build agent exited
clean every half minute and was restarted by its supervisor, a crash loop with nothing in the log
to say why. Only our own context ending ends the machine; an empty fetch, however it is reported,
is asked again.

mesh-admin merged commit e01d18e548 into main

2026-10-03 09:41:53 +00:00

mesh-admin deleted branch fix/an-empty-fetch-is-not-the-end

2026-10-03 09:41:53 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#234