net controller: bind routine node caches to expiring detail ownership - #787
Closed
Patrick W. Healy (phealy) wants to merge 2 commits into
Closed
Patrick W. Healy (phealy) wants to merge 2 commits into
Patrick W. Healy (phealy) wants to merge 2 commits into
Conversation
Move production legacy full and delta ownership to the UID-bound detail lifecycle. Read legacy delta bases and validation memos only from unexpired TTL snapshots, use compare-and-swap against replaced bases, and emit overview callbacks. Add a checked full-store API for ingestion errors while preserving the standalone legacy test helper. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: d2243398-6c36-4c3d-969e-7ed7bfb5b459
Use checked ingestion in JSON, protobuf, raw HTTP, and WebSocket full publications. Report retryable HTTP failure or explicit resync without advancing revisions when node identity or leader-local storage is unavailable. 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
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
Keep production node caches overview-only. Store legacy full/delta bases and identity memos exclusively in the UID-bound TTL detail store, require resync after base expiry or replacement, and fail checked ingestion explicitly when storage is unavailable.
Compatibility
Based on #786 after dashboard/CLI migration. Replaces the transitional passive observer with lifecycle binding. Legacy publishers still work, but routine caches no longer retain their detailed arrays. All five full-ingestion paths propagate failures without success ACKs or revision changes. Bulk serialization migration follows.
Validation
Full controller/shared-status race suites and scoped formatting/lint passed. Includes full/delta TTL, passive-to-bound transition, and raw HTTP/JSON/protobuf HTTP/WebSocket success and failed-store coverage. Immediate-parent diff below 1,000 changed lines.
Part of the draft lightweight-status stack based on #745. Node publishing default remains full until final activation.
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