NousResearch/hermes-agent

tree:0 clone auto-maintenance triggers runaway lazy-fetch

Cluster 127711. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #131679 on 2 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #131679. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #131679. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #131679, then check it covers your case.

Read #131679 Pick up a Lab task

In partial (tree:0) clones, git auto-maintenance—specifically commit-graph write --reachable—triggers an unbounded detached lazy-fetch loop, spawning thousands of git processes and consuming extreme memory. Members cover the bug report, a proposed fix to disable auto-maintenance in such clones, and related pack/commit-graph behavior.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#131679 A partial clone's .git stops growing: lazy-fetch packs fold on update and the commit-graph loop is off (#129712, salvage #129724, #127721)

merged to main

files: hermes_cli/gitlock.py, hermes_cli/update_cmd.py, hermes_cli/update_cmd_check.py, scripts/install.ps1, scripts/install.sh, tests/hermes_cli/test_gitlock.py, website/docs/getting-started/updating.md

1 PR closed without merging

From the close comments: done elsewhere 1

#127721 fix(install): disable auto maintenance in tree:0 clones · done elsewhere → 73c1715, 4e3fcd5, #131679, #127711

Closed issues · 1

Closed#127711tree:0 install clone: git auto-maintenance (commit-graph write --reachable) triggers unbounded detached lazy-fetch loop — 2,000+ git procs, 130 GB RSS on macOS / git 2.54

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.00 means 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 Lab

At a glance

Merged PRs: #131679
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 2 Oct 2026

For your agent

The same facts, typed.

cluster/127711.json
cluster/127711.md