Cairn

Cron run caller timeout leaves unknown execution state

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

These items address a bug where the hermes cron run command can leave agent-backed executions in an unknown state if the calling process times out or disconnects. The fixes involve detaching or keeping direct runs alive so a dead caller does not corrupt execution state.

Open issues1

  • Issue#102511[Bug]: `hermes cron run` can leave agent-backed executions in unknown state after caller timeout

Open PRs2

  • PR#102530fix(cron): keep direct runs alive after CLI timeout
  • PR#102538fix(cron): detach CLI/tool cron run so a dead caller cannot leave unknown
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/102511.json
cluster/102511.md