Cairn

Kanban worker shutdown signal handling fixes

NousResearch/hermes-agent · cluster 59799 · cron

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These items address how Kanban workers distinguish infrastructure SIGTERM signals from fast-reclaim signals, and how shutdown-related exits interact with retry budgets and the systemic crash breaker.

Open issues2

  • Issue#59799Kanban workers: distinguish infra SIGTERM and fast-reclaim foreign-host claims
  • Issue#62457[Bug]: Gateway-shutdown worker exits can trip the systemic crash breaker and failure_limit=1

Open PRs2

  • PR#60469feat(kanban): distinguish infra SIGTERM and fast-reclaim signals for workers (#59799)
  • PR#62790fix(kanban): preserve restart victims retry budget
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/59799.json
cluster/59799.md