b3e477f304
The post-update fleet version check slept 2s and probed once. On Windows the resume path relaunches the gateway detached, and it needs ~10s to boot (the Telegram polling reconnect) before it stamps gateway_state.json or answers the control socket. That race reported "no rows" for a healthy resume, exited 1, and triggered a full retry that re-killed the gateway the first attempt had just started — leaving it down and surfacing "Update failed (exit 1)". Poll a bounded window (up to 30s) for the resumed gateway to publish its identity, and only treat a persistently empty snapshot as verification failure. The fail-closed contract from #93406 is preserved: a gateway that genuinely never comes back still exits 1.
2 lines
11 B
Plaintext
2 lines
11 B
Plaintext
AlexGabbia
|