Verify shared workload publication and failed-generation isolation - #517
Merged
Merged
Conversation
…gh production processes
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
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.
Before this PR
The whole-backend process fixture used an obsolete publication request, APPLIED instead of STAGED, and summary payloads without frame lineage. It no longer exercised the current deployment contract.
After this PR
Two quantile roots publish one producer. The emitted plan passes the actual ASAPCollector library validator and runtime-config projection. Production control-plane and data-plane processes exchange a current staged plan and consume generation-bound OTLP checkpoints; both readouts return the expected values. An injected Collector staging failure leaves the old active plan and warm result unchanged, and a frame from the rejected generation is rejected.
Verification
Built the production control-plane binary and ran backend_process_e2e successfully. Collector acknowledgement is simulated; Collector plan decoding/projection uses its real library, not a duplicate backend schema. This does not claim a real Collector process or its raw-update loop ran. Quantile fixtures use integral ranks; arbitrary PromQL interpolation conformance is not claimed.
Stacked on #516. No automatic merge or independent review.