chore: sync the fork with upstream main - #7
Merged
Conversation
yordis
commented
Sep 13, 2026
yordis
commented
Member
- Upstream retired the bundle runtime in favour of packfile URI delivery, so the fork's bundle-era maintain test and the local clippy allowances beside it guard nothing any more and would only conflict on every future sync.
- What the fork exists for is untouched: the canary image pipeline, the pinned actions, the container protobuf fix and the test-tier watchdog.
- The canary waits on the new contract job too, because a tag that claims to be the newest green main has to mean every gate main runs was green.
Delete bundle routes, scheduler, crate, configuration, recipes and helpers. Preserve durable protobuf decoding and supported saved settings through a bounded read transition. Clone/fetch remain dynamic pending exact pack coverage and URI delivery. Store depth: remove optional bundle-list GET from v2 capabilities and narrated fetch; remove bundle list GET/CAS and compose from maintenance/import. Push and checkpoint budgets unchanged.
Checkpoint publication remains four healthy requests. Old checkpoint descriptors require one metadata GET instead of guessing their refs path. Push and warm-ref budgets remain unchanged.
Classify, fold, freeze and re-segment exact committed inputs with additive output publication and final-only retirement. Preserve indexed objects, shared code/meta membership, isolated resumable scratch and bounded delta resources. Maintenance adds one publication per physical output and a final seal CAS plus lease heartbeats. Ordinary push/read/checkpoint budgets are unchanged. Validated with Rust 1.97.1 just ci and 19 serial simulation cases.
Keep remote/gix and protected clients dynamic. Require authenticated exact live or retired membership for static pack/index bytes. Selection normally adds one coverage snapshot GET, with a shared three-attempt cap; index trailers are local bounded reads.
Port 123 model cases with exact negative controls and bounded JVM execution. Preserve unknown CAS outcomes, reject empty-ref pack publication, settle no-ops without history, and never replay ambiguous broker delivery. Claim nonces prevent content-token aliasing; exact lost-reply resolution adds one log GET only when the descriptor is listed.
Check raw indexed links in isolated cuts, repair invalid index identity with fresh inodes, and retain cross-process ownership through cancellation. Carry readiness only from a proven inventory and reject incomplete small downloads. Store cost: healthy cached indexes remain zero reads; corruption adds an index GET (HEAD only for unknown old sizes). Four concurrent downloads, no LIST. Added local checksum cost on inventory open. Validation: just ci (38 e2e), 19 serial simulations, 166 TLC cases, process-crash and corruption tests, final targeted Clippy.
Capture manifest/token/refs per CAS attempt, validate current indexes, and merge input/output OIDs with O(pack-count) cursors. Refuse lost unreachable objects or uncovered current tips before claiming a retirement log slot. Cost: no extra store reads with valid warm indexes; cold/bad indexes add GETs (HEAD for unknown sizes), at most four concurrent downloads. Adds full local ref capture and streaming index scan per seal attempt. No pack materialization or LIST. Validated with just ci (38 e2e), 19 serial simulations, 166 TLC cases and real-index refusal/recovery regression. Candidate push/import raw-boundary gates remain required.
A live commit-graph lock copied into rebuild scratch has no owner and prevents graph generation. Exclude Git lock files and test that the live source remains untouched. Prepare all race contenders before releasing any push, then assert exactly one winner. Validation: local just ci passed, including 38 active end-to-end tests and the deterministic scratch lock regression.
…nserving-lifecycle # Conflicts: # crates/walgit-server/src/rebuild.rs
…alidation # Conflicts: # .github/workflows/ci.yml
…sure-cache # Conflicts: # docs/spec/README.md
Remove bundle runtime and preserve ordinary Git clone/fetch
Add exact pack coverage and durable retirement foundations
Add conserving staged pack lifecycle and verified multi-pack bitmaps
Deliver proven packs through native Git URI negotiation
Check bounded publication contracts and correct ambiguous receipts
Validate pack indexes, raw links and readiness across restart
Prove indexed conservation and current tips before retiring packs
Upstream removed the bundle runtime in favour of packfile URI delivery, so the fork's bundle-era maintain test and the local clippy allowances beside it guard nothing any more and would only conflict on every future sync. What the fork exists for is untouched: the canary image pipeline, the pinned actions, the container protobuf fix and the test-tier watchdog. The canary now waits on the new contract job too, since a tag that claims to be the newest green main has to mean every gate main runs was green. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
PR SummaryHigh Risk Overview CI now runs Reviewed by Cursor Bugbot for commit 5bda1e7. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Important Review skippedToo many files! This PR contains 229 files, which is 129 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (229)
You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 054f985. Configure here.
The canary publish needs this job now, so its verdict decides whether a main commit is treated as green and shipped. A moving tag in the job that renders that verdict could pass a contract that never held, which is the same reason the publishing job has been pinned all along. Signed-off-by: Yordis Prieto <yordis.prieto@gmail.com>
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
2 participants
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.