docs(convergence): the not-modelled list no longer denies the re-convergence it demonstrates #2028
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!2028
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1118-2017"
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/CONVERGENCE.mdsaid, in "What this does not model", that "Changing a link after power-on and watching the network re-converge is not modelled; the schedule is computed from the topology as it stands", and that a cable pulled mid-convergence "is a separate feature". Both bullets date from #1050; #1058 landed exactly those two behaviours and added the "Re-convergence: a cable is pulled" section to this same page without pruning the list.Evidence from the engine:
engine/convergence.js:149-200—buildSchedule(topo, { fromMs })re-bases every entry onfromMsand prepends achangeentry at that instant.engine/simulator.js:459—getConvergence()passesfromMs: this.topo.lastChangeAtMs || 0.convergereports 30000 ms;link down l1 at 5000answers "Network converges again at 35000 ms" andconverge at 20000showschange 5000 ms the link state changedwith stp pending;link down l2 at 9000answers 39000 ms and the change entry moves to 9000, the earlier deadline gone.The two stale bullets become one true one: only the most recent change is kept, so a second pull re-bases the schedule rather than interleaving with the first.
Docs guards unchanged: syntax-check 422 files OK; docs-cli-transcript 4/0; docs-show-commands 7/0; no-form-help-key 81/0; help-completeness 8/0.