Cairn
NousResearch/hermes-agent

Cron worker kill/failure not recorded on job

Cluster 120328 · cron. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 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
Nothing open on GitHub.

These items address cases where cron workers killed or failing after job adoption leave the job record without updated status, incident, or failure delivery. The work involves detecting and recording such outcomes on the job.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1 · other 1

  • #120347 fix(cron): project recovered worker failures · done elsewhere
  • #120360 cron: record killed post-adopt worker on the job (incident, delivery, log) · other
  • #120391 fix(cron): record a restart-safe worker's unknown outcome on the job · closed without comment
Closed issues · 1
  • Closed#120328[Bug]: cron worker killed after adoption (e.g. OOM) leaves the job record untouched — no last_status, no incident, no failure delivery
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.50: 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
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/120328.json
cluster/120328.md