NousResearch/hermes-agent
Fix cron timeout doc: 600s inactivity not 3-min hard interrupt
Cluster 55038 · skills. 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.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA documentation error described the cron scheduler as having a 3-minute hard interrupt per run, when it actually uses a 600-second inactivity timeout. These issues and PRs address correcting that inaccuracy.
Open issues1
- Issue#55038[Docs]: bundled hermes-agent skill says cron has a "3-minute hard interrupt per run" — scheduler actually uses a 600s inactivity timeout
Open PRs1
- PR#55117docs(cron): fix bundled skill doc to say 600s inactivity timeout not 3-minute hard interrupt (fixes #55038)
1 PR closed without merging
From the close comments: duplicate 1
-
#55194 docs: fix cron invariant — 600s inactivity timeout, not 3-minute hard interrupt · duplicate →
#55117,#55038
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.00means 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 LabAt a glance
- Subsystem
- skills
- Closed issues
- 0
- Attempts
- 1 PR closed without merging