Cairn
NousResearch/hermes-agent

Stable update ancestry probe timeouts in git merge-base checks

Cluster 139091 · hermes cli. Data as of

2 open items. Fix merged in #139079 on 15 Oct 2026. Check it covers your case.

The short answer

1open issue
1open PR
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #139079. 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
1 issue and 1 PR.

The members concern the stable update path's 10-second git merge-base/ancestry probe timing out, including when commits are local in a partial clone with commit-graph writes disabled. They include a bug report and several change proposals with different approaches (tolerating timeouts, answering locally after a commit-graph write, avoiding refusal of the stable channel); outcomes are not established here.

Open issues1

  • Issue#139091[Bug]: stable update 10s merge-base probe times out even when both commits are local (partial clone, commit-graph writes disabled)

Open PRs1

  • PR#139506fix(update): answer the ancestry probe locally after one commit-graph write

Fixes on record

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

  • #139079 hermes update no longer refuses the stable channel when git is slow to find the unfetched release (#137646, salvage #137649)

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/source_releases.py, tests/hermes_cli/test_gateway_chat_native.py, tests/hermes_cli/test_stable_forward_only_shallow.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #139107 fix(update): tolerate stable ancestry probe timeouts · superseded by another PR → 3bdb82d, #139079, #137649
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.50: 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
Merged PRs
#139079
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
15 Oct 2026

For your agent

The same facts, typed.

cluster/139091.json
cluster/139091.md