Repository navigation
v0.1.3
seat-pace can now fall back to another machine when an account's reading machine is down (#19, PR #20).
[[account]]
machine = ["office", "home"] # preferred first; a single string works as before- A machine later in the list first asks the fleet, with
robot-council api GET /api/lanes, whether an earlier machine has an active session. If one does, it doesn't read. If the command is missing or the fleet can't be reached, it doesn't read either, and says why on stderr. It never assumes the earlier machine is down. - If a machine's last local log row is more than 1.5 intervals old, its next reading counts as a fresh start and runs no
on_change. - A verdict change that happened while another machine was reading isn't reported on takeover.
- A machine that's present but whose scheduler is broken isn't detected.
read,logandwatchstill refuse to run on a machine that isn't in the list.docs/pacing.md,docs/coordinators.md,docs/getting-started.mdandexamples/seats.tomldescribe the list.
Not yet verified: the fleet's answer against a live fleet. Its shape comes from the core and cli source, and the tests replay a synthetic answer.