NousResearch/hermes-agent
Dispatcher retry logic and resilience improvements
Cluster 30417 · cron. Data as of
1 open item. Fix attempted, not merged.
The short answer
1open issue
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 3 PRs 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 0 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items concern making the kanban dispatcher more resilient through adaptive retry strategies, model escalation, exponential backoff, and handling of edge cases like SQLite I/O errors, spawn-crash loops, and archived-parent promotion.
Open issues1
- Issue#30417Dispatcher resilience: deterministic spawn-crash loop, transient SQLite I/O latches dispatch off, archived-parent silently promotes children
Open PRs0
3 PRs closed without merging
From the close comments: closed without comment 1 · superseded by another PR 1 · other 1
- #30608 feat: adaptive retry with model escalation for kanban dispatcher · closed without comment
- #30620 feat(cli): adaptive retry with model escalation for kanban dispatcher · other
-
#31932 fix(gateway): replace permanent corrupt-board latch with exponential backoff · superseded by another PR →
c94ad89
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.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
- cron
- Closed issues
- 0
- Attempts
- 3 PRs closed without merging