Cairn
NousResearch/hermes-agent

Kanban stale failure error and respawn guard handling

Cluster 121281 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 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 1 PR.

These members concern kanban cards where a manual blocked-to-ready promote retains a stale last_failure_error, and where blocker_auth is described as parking the card. Two items propose changes: clearing the stale error on promote and basing the respawn guard on run outcomes rather than error text.

Open issues1

  • Issue#121281kanban: a manual `blocked` → `ready` promote keeps the stale `last_failure_error`, and `blocker_auth` parks the card forever

Open PRs1

  • PR#121292fix(kanban): clear stale failure error on manual promote

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.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
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/121281.json
cluster/121281.md