docs(cli): a lost echo prints no timeout line, because the console stopped printing one #2208
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!2208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/1119-2047"
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/CLI.md's "Why an echo never came back" still showed the answer #2204 removed.Untrue: two "after" transcripts in that section ended with
Request timed out (seq 0)(and four such lines under the 4-echo ping), and two sentences claimed that line was still printed "only where the timeout really did expire" and that "the timeout line already said what happened".Evidence:
engine/cli.js_pingReplyLines()(around line 4434) prints the marks line and the success rate and nothing else - "There is deliberately no per-echo sentence after the rate" - and #2204 deleted theRequest timed out (seq N)push along with theReply fromlines. Replaying both documented sessions against the engine prints:Fix (docs only): dropped the timeout lines from both transcripts (both replay byte for byte, prompt
r1>), corrected the two prose claims to point at the.on the marks line, and added one sentence saying the per-echo timeout line is gone with theReply fromlines. The past-tense "the console printed the timeout and discarded it" example above them is left as history.Guards, before and after: syntax-check 466 files OK / 466 OK; docs-cli-transcript 9 pass / 9 pass; docs-show-commands 7 / 7; no-form-help-key 81 / 81; help-completeness 8 / 8; doc-catalog-counts 43 / 43; doc citations 358 / 358.