Skip to content

net: bridge legacy status publications into expiring details - #780

Closed
Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-ws-source-ownershipfrom
phealy/lightweight-status-legacy-bridge
Closed

Patrick W. Healy (phealy) wants to merge 1 commit into
phealy/lightweight-status-ws-source-ownershipfrom
phealy/lightweight-status-legacy-bridge

Conversation

@phealy

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

Copy link
Copy Markdown
Contributor

Purpose

Feed accepted legacy full/delta publications into the expiring per-node diagnostic API so migrated clients can reuse data from nodes with unreachable HTTP endpoints.

Compatibility

Based on #779. Existing full cache, delta bases, callbacks, and publishing defaults are unchanged. Legacy updates do not fulfill unrelated pending refresh requests; summaries and source changes do not renew detail TTL. This transitional observer precedes client migration and thin-cache activation.

Validation

Focused controller race tests covering legacy observation, request lifecycle, transport, and source ownership; scoped formatting/lint clean. Immediate-parent diff: 209 added lines.

Part of the draft lightweight-status stack based on #745. Default activation remains pending.

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

Observe authenticated full/delta cache writes in publication order while preserving existing full bases and bulk callbacks. Make UID-bound cached results available to migrated clients without requiring a reachable node HTTP endpoint. Reuse completed cache associations, keep correlated pending requests isolated, and exclude reads, source changes, and summaries from TTL refresh.

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 #755 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