Skip to content

fix: harden physical-plan activation and frame lineage - #588

Merged
zzylol merged 1 commit into
mainfrom
fix/pr585-correctness
Sep 4, 2026
Merged

zzylol merged 1 commit into
mainfrom
fix/pr585-correctness

Conversation

@zzylol

@zzylol zzylol commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up correctness fixes for #585:

  • propagate retired-generation delivery failures so failed cutovers are never reported APPLIED
  • preserve committed CMS width/depth in the Rust runtime projection
  • align aggregator-wide checkpoint resets with per-lineage frame sequencing
  • scope frame lineage by plan ID/version in Go and Rust
  • persist the last APPLIED OpAMP generation atomically across Collector restarts
  • allow one QueryPlan query ID to own multiple materializations
  • add regression coverage for each boundary

Validation

  • go test ./... in asap-precompute-go
  • go test ./... in opentelemetry-collector-contrib-patch/processor/asapedgeprocessor
  • cargo test --manifest-path asap-precompute-rs/Cargo.toml
  • git diff --check

The existing one-executor-per-metric limitation remains explicitly fail-closed and requires a separate runtime registry redesign.

@zzylol
zzylol merged commit 6726697 into main Sep 4, 2026
1 check passed
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