drop the leftover matrix sweep references in docs and comments
This commit is contained in:
parent
6dbb18b6d4
commit
bdda69a080
1 changed files with 9 additions and 10 deletions
|
|
@ -196,17 +196,17 @@ fn boot_action(wanted: Option<crate::power::Wanted>, fresh: bool, running: bool)
|
|||
}
|
||||
}
|
||||
|
||||
/// Submit the boot-time forge/matrix/knowledge/wanted-state sweeps as DAG
|
||||
/// nodes — `ForgeSweep`, `MatrixSweep`, `KnowledgePull`, `WantedPull`. Unlike
|
||||
/// Submit the boot-time forge/knowledge/wanted-state sweeps as DAG
|
||||
/// nodes — `ForgeSweep`, `KnowledgePull`, `WantedPull`. Unlike
|
||||
/// [`submit_boot_tree`] this runs on **every** boot, quiet or not: these
|
||||
/// aren't config-drift work, they're startup housekeeping that always needs
|
||||
/// to happen, and the point of moving them here is exactly so they show up
|
||||
/// as real work on the dashboard instead of an invisible `tokio::spawn` that
|
||||
/// only surfaces on failure. Four independent, build-slot- and lease-exempt
|
||||
/// only surfaces on failure. Three independent, build-slot- and lease-exempt
|
||||
/// roots — no dependency edges between them, matching the existing
|
||||
/// `Reconcile`-root pattern in [`boot_nodes`]. `MatrixSweep` and
|
||||
/// `KnowledgePull` hold their sweep's own resource, so each queues behind any
|
||||
/// pass of the same sweep already running.
|
||||
/// `Reconcile`-root pattern in [`boot_nodes`]. `KnowledgePull` holds its
|
||||
/// sweep's own resource, so it queues behind any pass of the same sweep
|
||||
/// already running.
|
||||
fn submit_startup_sweep_nodes(coord: &Arc<Coordinator>) {
|
||||
use crate::job_queue::NodeKind;
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue