Cairn
NousResearch/hermes-agent

Kanban dispatcher double-counting bug with dual limits

Cluster 63466 · 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 items all concern the same bug where the Kanban dispatcher incorrectly double-counts running workers when both max_spawn and max_in_progress are configured simultaneously. The group includes a bug report and at least one fix attempt addressing this specific counting issue.

Open issues1

  • Issue#63466Kanban dispatcher double-counts running workers when max_spawn and max_in_progress are both set

Open PRs1

  • PR#63548fix(kanban): dispatcher double-counts running workers when both max_spawn and max_in_progress are set

1 PR closed without merging

From the close comments: duplicate 1

  • #63471 fix(kanban): resolve double-count when both max_spawn and max_in_progress are set · duplicate → #63466, #33326, #56837
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/63466.json
cluster/63466.md