Kanban fresh claim heartbeat timestamp bug fix

NousResearch/hermes-agent · cluster 119155 · 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.

A bug where a freshly claimed kanban job inherited the previous run's last_heartbeat_at timestamp, causing release_stale_claims to incorrectly reclaim and SIGTERM a live worker. The fix ensures a fresh claim seeds last_heartbeat_at correctly to prevent premature reclamation.

Open issues1

  • Issue#119155[Bug]: kanban fresh claim inherits the previous run's last_heartbeat_at, so release_stale_claims reclaims (and SIGTERMs) a live worker

Open PRs2

  • PR#119157fix(kanban): reset heartbeat on fresh claim
  • PR#119199fix(kanban): a fresh claim seeds last_heartbeat_at so release_stale_claims cannot reclaim a live worker
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.