Cairn

Kanban worker fingerprint start-time comparison and drift tolerance

NousResearch/hermes-agent · cluster 135344 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

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

The members concern the kanban dispatcher's _pid_recycled check, which reportedly compares composed worker fingerprints by exact equality, so live macOS workers may be treated as recycled and duplicated. Two members are fixes proposing start-time drift tolerance for composed (and in one case legacy) fingerprints.

Open issues1

  • Issue#135344kanban dispatcher: _pid_recycled compares the composed worker fingerprint by exact equality, so live macOS workers read as recycled and get duplicated

Open PRs2

  • PR#135355fix(kanban): compare the composed worker fingerprint's start time with drift tolerance
  • PR#138328fix(kanban): tolerate start-time drift in composed and legacy worker fingerprints
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/135344.json
cluster/135344.md