Cairn

Kanban worker process lifecycle and termination fixes

NousResearch/hermes-agent · cluster 22927 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

2open issues
2open PRs
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue 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
2 issues and 2 PRs.

These issues and pull requests address bugs where Kanban worker processes were not reliably terminated when tasks were completed, blocked, or archived, including zombie process problems on Windows and a race condition between task state changes and worker startup.

Open issues2

  • Issue#22927[Bug]: Kanban task state can change between dispatch and worker startup — no guard in worker init
  • Issue#61923Kanban worker zombie process on Windows: complete_task doesn't terminate OS process, no process-state sync

Open PRs2

  • PR#61967fix(kanban): stop zombie workers after complete (#61923)
  • PR#131470fix(kanban): guard worker startup against dispatch-state race

3 PRs closed without merging

From the close comments: superseded by another PR 3

  • #57602 fix(kanban): terminate worker process on block/archive/complete (#57596) · superseded by another PR → #31365
  • #57713 fix(kanban): terminate workers when tasks are blocked or archived · superseded by another PR → #57704, #31829, #35327, #57548, #28154, #57713, #31365, #57536, #57248, #57696, #47821
  • #116698 fix(kanban): reject stale worker claims at startup · superseded by another PR
Closed issues · 1
  • Closed#57596Kanban worker process can survive after task is blocked/archived
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.20: 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
agent
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/22927.json
cluster/22927.md