Cairn
NousResearch/hermes-agent

Kanban blocker_auth retry and failure limit fixes

Cluster 73369 · cron. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

These issues and fixes address a bug where the kanban dispatcher could leave blocker_auth tasks stuck in a ready state indefinitely, and ensure that blocker_auth failures are properly counted toward the failure limit with bounded retry attempts.

Open issues1

  • Issue#73369Kanban dispatcher can leave blocker_auth tasks permanently ready

Open PRs2

  • PR#73371fix(kanban): bound blocker auth respawn retries
  • PR#73494fix(cron): make kanban dispatcher count blocker_auth failures toward failure_limit

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #142737 fix(kanban): respawn guard decides from run outcomes, never from error prose · stale or abandoned
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
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/73369.json
cluster/73369.md