operator-side republish heartbeat for cassette operations #47
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
An operation is published only when an operator records one. If the relay or nostrclient is unreachable at that moment the op is still recorded, deliberately, since the notes physically moved, and the endpoint returns 503 saying it will ride out with the next publish. But nothing publishes on its own, so "the next publish" means the next time a human touches the dashboard.
The machine already heartbeats its state every 5 minutes. The operator should do the same for the ops window, so the channel self-heals in both directions rather than one.
Small: a periodic task walking active machines that have unacked ops in their window and republishing. Skip machines with nothing pending.
Context:
docs/adr/004-cassette-state-synchronization.mdin aiolabs/bitspire, under "Status of implementation", where this is recorded as the one gap left open on purpose. Shipped in #46.