plans: a flow is published to a browser that drops it, and the console has no word for a connection #2339
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!2339
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1121-0037"
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?
Forward plan only, no code.
openFlow()produces a real conversation (measured: 4000 bytes,established, 3 segments, 9 packets) andfullState()already publishes every record throughdescribeFlow()(server/index.js:275-283,:414-415). Nothing reads it:grep -n "\.flows" web/app.jsreturns nothing — the browser paints flow events (:2762-2769) and no table.show tcp/show tcp brief/show tcp statistics/show sessionsall answer% Invalid show command;SHOW_VIEW_WORDS(engine/cli.js:203-217) has notcpentry, and a comment atserver/index.js:414claims ashow flowscommand that does not exist.engine/simulator.js:4304,:4333), soflowsRefusedand theflow-refusedevent are the only trace.rec.stalled(:4379) is read by nothing and cannot be set: every segment of one flow shares one tuple and one path inside one call.The plan orders six steps: vendor research for
show tcp brief; the console view; a Flows panel over the state already on the wire; a way to open one from the UI (labelled needs Jay approval); a refusal footer; and the docs plus the stale comment, including deletingstalled.Measured on
e2ac102e, 2026-11-21. Closes no open issue — the queue is #2336-#2338 (PRs open), #130 and #803.