Expand description
Whether an in-flight activity can still reach a worker. Whether an in-flight activity can still reach a worker.
ActivityStarted is recorded by the engine at DISPATCH time, atomically with
its ActivityScheduled and before any worker has leased the work (see
aion::durability::recorder::fan_out and the single-dispatch seam in
aion::runtime::nif_activity_dispatch). So a started, unterminated activity
means “the engine handed this to the fleet”, not “someone is working on it”,
and a dispatch to a task queue nobody serves is byte-for-byte
indistinguishable in history from one a worker is executing right now. The
projected status is Running for both, correctly — status is a projection of
history, and history genuinely contains no terminal event.
What history alone cannot say, the live fleet can. This module joins the two:
the run’s own recorded dispatch addresses against the SAME poller census and
the SAME classify verdict the dispatcher’s selection wait uses
([super::wait]). There is no second notion of “is anyone serving this” here
— a disagreement between what an operator reads and what a dispatch does
would be worse than the silence it replaces.
The healthy case is silent by construction: classify returns None for
an address with a live compatible worker, so a run whose activity is genuinely
being executed produces no entry at all.
Structs§
- Activity
Reachability - The live fleet seams an in-flight activity’s reachability is judged against.
- Open
Activity - One activity the active run segment records as dispatched and unterminated.
Functions§
- open_
activities_ in_ active_ segment - The activities the run’s active segment records as dispatched and not yet terminated, in the order the ordinals were opened.