Roll-up: a workspace whose container was removed outside Nexus reads as "nothing needs you" #198
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
lz/agent-nexus#198
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found in the final review of #155's branch (
feat/mcp-status). Same class as theexitedhole that branch closes, and it is still open.The case
A container removed outside Nexus (
docker rm, or a daemon wipe) leaves itsworkersrow atstatus: 'running'andprovision_phase: null, while the fleet store holds no entry. Solive_statusisnull.workspaceProblem($lib/attention-rollup.ts) only flagsexitedforlive_statusofexitedordead. It readsnullas "no observation", which is correct for a workspace the stream simply has not reconciled yet (AGENTS.md fact #41: an absence of information is not a diagnosis).isRunningfalls back tostatuswhenlive_statusis null, so the sessions derive from a staleclaude_alive. Depending on what was last recorded,nexus_get_statusreports one of two wrong answers:erroreditems, each saying "Restart it", when the real remedy is at the workspace level.What distinguishes it
nullis ambiguous today: not reconciled yet and container gone look the same. Only the second needs the operator. The fleet layer already knows the difference after a reconcile, becausereconcileFleetlists every managed container. An orphan row, one with no container at all, is a positive observation of absence, not a missing one.Shape of a fix (not designed)
Let the store carry "reconciled, and no container exists" as a distinct state, so the roll-up can report a workspace problem such as
missingwith the action "Its container is gone. Delete the workspace, or start it to recreate." Two things to keep in mind:startWorker's recreate path: it destroys and recreates a container while the row survives, so a transient "gone" must not flash an item.Rare in practice. Filed so the
exitedfix is not mistaken for full coverage of "the container is not what Nexus thinks".