Cairn

isolate network git fetches in own process group

NousResearch/hermes-agent · cluster 124794 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These items address a bug where a stalled or timed-out network git fetch during updates spawns an unbounded recursive process tree that cannot be fully reaped. The fix involves running the fetch in its own process group so a timeout or kill signal terminates the entire tree.

Open issues1

  • Issue#124794Updater network git calls on tree:0 partial clones with git < 2.44 spawn an unbounded recursive fetch process tree (missing process-group isolation)

Open PRs2

  • PR#124809fix(update): reap a stalled network fetch's whole process group
  • PR#124870fix(update): run network git in its own process group so a timeout reaps the whole fetch tree
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

Subsystem
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/124794.json
cluster/124794.md