Skip to content

net-node: respond immediately to WebSocket diagnostic commands - #776

Closed
Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-node-reply-statefrom
phealy/lightweight-status-node-ws-details
Closed

Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-node-reply-statefrom
phealy/lightweight-status-node-ws-details

Conversation

@phealy

@phealy Patrick W. Healy (phealy) commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Scope

Stacked on the node reply-state layer, with controller dispatch/receipt already in the stack. Wires authenticated WebSocket commands to immediate one-shot collection and correlated responses. Commands and detail ACKs do not clear ordinary publication ACK state; retries preserve request deadline and temporary payload ownership. Advertises detail capability when the responder is available.

364 changed LOC. Legacy publishing and the transitional full default remain.

Validation

Node/controller package race suites passed after stacking; scoped formatting/lint and node build passed during implementation.

Lightweight status draft stack

Base: #745. Each layer targets the preceding branch and remains draft.

#746 -> #747 -> #748 -> #750 -> #751 -> #752 -> #753 -> #754 -> #755 -> #756 -> #757 -> #758 -> #759 -> #760 -> #761 -> #762 -> #763 -> #764 -> #765 -> #766 -> #767 -> #768 -> #769 -> #770 -> #771 -> #772 -> #773 -> #774 -> #775 -> #776 -> #777 -> #778 -> #779 -> #780 -> #781 -> #782 -> #783 -> #784 -> #785 -> #786 -> #787 -> #788 -> #789 -> #790 -> #791 -> #792 -> #793 -> #794 -> #795 -> #796 -> #797 -> #798 -> #799

Serialize one-shot responses on the existing writer independently of pending publication ACKs. Preserve cached replies across reconnects, advertise support, reject expired work, and proactively release payloads at deadline or shutdown.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d2243398-6c36-4c3d-969e-7ed7bfb5b459
This was referenced Sep 16, 2026
This was referenced Sep 16, 2026
@phealy

Copy link
Copy Markdown
Contributor Author

This PR was mistaken churn from splitting the lightweight-status work into unnecessarily small PRs. That was my mistake, not a requirement from the user.

Its changes are preserved in #774 within the user-approved, consolidated 12-PR draft stack. Closing this superseded PR; the implementation is not being discarded, and nothing has been merged into main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant