NousResearch/hermes-agent
Cold-start git add timeout and index lock issues
Cluster 127732 · agent. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items concern a scenario where a project with no git ref causes a cold 'git add -A' to exceed its timeout budget, and the resulting stale index lock permanently blocks further operations. The cluster addresses both giving this cold-start path its own timeout budget and cleaning up the orphaned lock file.
Open issues1
- Issue#127732`checkpoint_manager`: a project with no ref can never build one (cold `git add -A` exceeds the timeout cap), and the timeout leaves an index lock that wedges the project permanently
Open PRs1
- PR#127742fix(tools): reap the stale index lock a timed-out git add leaves behind
1 PR closed without merging
From the close comments: other 1
- #127857 checkpoint: give the no-ref cold-start staging add its own budget · other
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
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 1 PR closed without merging