Skip to content

fix(graph): surface failed sealed generation retirement - #4716

Closed
ScriptedAlchemy wants to merge 3 commits into
masterfrom
fix/graph-sealed-retirement-failures
Closed

ScriptedAlchemy wants to merge 3 commits into
masterfrom
fix/graph-sealed-retirement-failures

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Nov 3, 2026 •

Copy link
Copy Markdown
Owner

Scope

Refs #4616; does not complete sealed-generation collection.

Return a typed error when a retired or quarantined generation's sealed directory cannot be removed, including retries after its in-memory reader has gone. An absent directory remains an idempotent success. Refuse a poisoned reader registry; warn on failures in the separate best-effort staging cleanup path. Collection eligibility, reader protection, leases and journals are unchanged.

The regression places a regular file in the exact artifact directory slot, requires deletion to fail without losing those bytes, then verifies successful retry and idempotent replay.

Shared CI fixture repair

Commit 5e1906a371970119b2c2c4f029bc470fa2407ff4 applies the exact reviewed fix from #4731. This branch's private Linux run failed two ignored-dependency admission tests while waiting for a generation-publication event that could fire before subscription. The fixture now uses its existing stronger fresh serving-generation check directly. All behavioral assertions and that check's deadline remain intact.

The original fixture blob was identical to #4731's parent; the published replacement is exactly 9135cf4f9077156831e3f0bb0141f40b99503b65. This is a targeted follow-up on the existing branch, not a history rewrite or a merge into master.

Validation

The shared fixture repair passed native Linux on #4731 (private run 41665062193). That result does not validate this updated branch's graph-retirement integration. Fresh exact-head CI is pending in https://github.com/ScriptedAlchemy/tracedecay/actions/runs/41706621169.

No local Rust compilation, Bazel tests or rustfmt ran in this repair environment. No assertions, admission controls or test workloads were weakened. Full applicable hosted validation remains required before merge.

Ordinary missing-generation sweeps, retention fairness, unsafe-artifact isolation, reclaim guidance and the reported large-store resource measurements remain outside this PR. Keep #4616 open.


Devin Review

@changeset-bot

changeset-bot Bot commented Nov 3, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 5e1906a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 Devin Review: 1 flag

Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)

Devin Review

Apply the already-reviewed fixture repair from fbca068 (#4731) to this branch after its private Linux run failed at the redundant generation-publication wait. The original fixture blob matches exactly.

Keep the stronger fresh serving-seat wait and all admission assertions. No deadline increases, production changes, or validation skips.

The shared repair passed native Linux on #4731; this branch's new integration still requires its own hosted Bazel validation. No local Rust execution is claimed.
@ScriptedAlchemy

Copy link
Copy Markdown
Owner Author

Consolidated into #4742 (integrate/open-pull-requests) at the captured head shown in its description, as requested. Continue review and further fixes on #4742. This closure does not assert CI readiness; the replacement remains draft. Source branch retained.

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