LINK-STATE: the saved lab has no lastChangeAtMs, so stop claiming it does #1571
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!1571
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1116-0016"
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?
docs/LINK-STATE.mdsaid, under Persistence, that "the topology records"lastChangeAtMs": 10000", and a paragraph up top said the change instant "survives save/load".The engine has said otherwise since #1331:
engine/topology.js:762�lastChangeAtMsis deliberately NOT written: "an instant in a run, and a run ends". The serialized document has keysformat,version,seq,devices,links,layout,flowsand nothing else.engine/topology.js:902�fromJSON()derives the clock from the newest cablestateSinceMs.Probe on a two-switch board,
linkDown(l1, { atMs: 10000 }):{"id":"l1",...,"state":"down","stateSinceMs":10000}lastChangeAtMsTopology.fromJSON(saved).lastChangeAtMs->10000The outage does come back (
state: downis restored, the window is right), so only the "the file records the instant" claim was false.docs/ARCHITECTURE.mdalready described the derived clock; this page was the last one quoting the old document. Reworded both sentences to say what is written and what is derived.Guards: syntax-check 327 files OK; control-bytes clean; doc-citations 350 citations, 5 suspects inside the 40-line allowance; doc-catalog-counts 24; docs-show-commands 7; help-completeness 8; help-key-works-in-every-prompt 9 pass; repo-paths 8 � unchanged before and after (docs-only edit).