hive-c0re: the port range is every agent's, not the sub-agents'
Two more statements of the claim the previous commit removed: the snapshot field called the clusters "sub-agents", and WEB_PORT_BASE's own doc called the range sub-agent-only while the function that reads it says "every agent including the manager" three lines below. docs/process/gotchas.md already had this right.
This commit is contained in:
parent
877e8bcf81
commit
89b4e8afb6
2 changed files with 6 additions and 6 deletions
|
|
@ -56,9 +56,9 @@ pub(super) struct StateSnapshot {
|
|||
/// survive after a destroy-without-purge. The operator can re-spawn
|
||||
/// with the same name to resume, or PURG3 to wipe them.
|
||||
tombstones: Vec<TombstoneView>,
|
||||
/// Sub-agents whose FNV-1a hashed web UI port collides with at
|
||||
/// least one other agent. Operator resolves by renaming. The
|
||||
/// dashboard renders a banner at the top listing each cluster.
|
||||
/// Agents whose FNV-1a hashed web UI port collides with at least
|
||||
/// one other. Operator resolves by renaming. The dashboard renders
|
||||
/// a banner at the top listing each cluster.
|
||||
port_conflicts: Vec<PortConflict>,
|
||||
/// Inputs in `meta/flake.lock` the operator can selectively
|
||||
/// `nix flake update`. Hyperhive first, then `agent-<n>` rows.
|
||||
|
|
|
|||
Loading…
Reference in a new issue