docs: drop statements about absent things, state current behaviour
This commit is contained in:
parent
abda781eef
commit
788542ba75
6 changed files with 21 additions and 37 deletions
|
|
@ -284,11 +284,8 @@ reconcile_), so there is no durable-recovery machinery to go wrong.
|
|||
|
||||
### Cancel, history
|
||||
|
||||
Every submit enqueues a fresh DAG; a multi-agent DAG has no single agent
|
||||
to key a dedup on.
|
||||
|
||||
Cancel only applies to DAGs that are still fully queued (an in-flight nix build isn't
|
||||
interruptible) — each op is one DAG, so there are no child DAGs to cascade to.
|
||||
interruptible).
|
||||
Roll-up state: `Failed` if any node failed, else `Running` / `Queued` /
|
||||
`Cancelled` / `Done`. The snapshot retains the 50 most recent terminal
|
||||
DAGs — a flat cap over the whole sorted list, not per template, since
|
||||
|
|
|
|||
Loading…
Reference in a new issue