Cairn

Retry and fallback for rate-limited update fetches

NousResearch/hermes-agent · cluster 105857 · 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 issues and PRs address missing retry and fallback behavior when GitHub update fetches return HTTP 429 (rate-limited) responses, particularly for repo-scoped requests. Proposed fixes involve bounded retries with existing credentials and degrading to an alternative update path such as a ZIP-based fallback.

Open issues1

  • Issue#105857hermes update has no retry or fallback for persistent repo-scoped HTTP 429

Open PRs2

  • PR#105870fix(update): retry repo-scoped 429 fetches and fall back to guarded ZIP update
  • PR#119603fix(update): retry a rate-limited GitHub fetch with the user's existing credential (#105857)
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/105857.json
cluster/105857.md