Parked-branch verification issues in partial clones
Cluster 124767. Data as of
Nothing open on GitHub. Fix merged in #132378 on 6 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #132378. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern correctness and safety problems with the parked-branch guard check during updates, specifically around spurious skips and unintended large fetch behavior in partial (tree:0) clone environments.
Open issues0
Open PRs0
Fixes on record
-
#132378 hermes update: the parked-branch check no longer lazy-fetches a partial clone into a 180 GiB pack runaway (#131444, salvage #124777)
files:
hermes_cli/update_cmd_git.py,tests/hermes_cli/test_update_parked_branch_guard.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#124777 fix(update): verify a parked branch from the commit graph before git cherry · done elsewhere →
cefe1db,85aa4b3,#132378,#131444
Closed issues · 1
- Closed#124767hermes update: parked-branch guard verification can skip spuriously on partial (tree:0) clones
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #132378
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 6 Oct 2026