6739bb903d
Every docs directory moves under 1-getting-started, 2-handbook, 4-implementation or 5-project; the options reference (section 3) comes from the website and has no directory here. trust-boundary stays whole under the handbook for now. web-ui, swarm and tools split between handbook and implementation, and the command-line references move to 2-handbook/reference. Links, path references in code and nix, and the docs index follow the moves; no page content changes.
23 lines
1.1 KiB
Rust
23 lines
1.1 KiB
Rust
//! Vocabulary hive-c0re's job queue shares with its clients: the
|
|
//! scheduler's lifecycle [`State`].
|
|
//!
|
|
//! A `Source` enum lived here too — where a job came from, rendered as the
|
|
//! "why" chip. It was a field on the DAG container, and it went with it: a
|
|
//! job is its nodes now, and a node says what it does rather than who asked
|
|
//! for it.
|
|
//!
|
|
//! **The typed `DagView`/`NodeView` projection that used to live here is
|
|
//! gone.** One graph is served one way now — `hive_jobq_wire`'s generic
|
|
//! `GraphNode`, over the `QueueNodes` socket request and
|
|
//! `GET /api/jobq/graph` — so there is no second shape to keep in
|
|
//! agreement with the first. Queue internals (node kinds, edges,
|
|
//! scheduling) live in `hive-c0re::job_queue`.
|
|
//! Semantics: `docs/4-implementation/scheduler/coordinator.md::Job queue`.
|
|
|
|
pub use hive_jobq::State;
|
|
|
|
/// Node id. Carries the scheduler crate's globally-monotonic node id
|
|
/// (`hive_jobq::NodeId`) verbatim on the wire — unique across all DAGs, not
|
|
/// just within one. Consumers treat it opaquely (grouping + dep matching),
|
|
/// so the widening from the old dag-local `u32` is transparent.
|
|
pub type NodeId = u64;
|