Cairn
NousResearch/hermes-agent

Cron config error message clarity improvements

Cluster 81420 · cron. 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.

These items relate to improving the accuracy of a RuntimeError message in cron model resolution, where the reported cause ('model.default missing or empty') does not reflect the actual underlying issue (config.yaml being unreadable). The group covers the bug report and associated fix attempts.

Open issues1

  • Issue#81420Cron model-resolution RuntimeError claims "model.default missing or empty" when actual cause is config.yaml being unreadable

Open PRs1

  • PR#81426fix(cron): name the real cause when no model resolves

1 PR closed without merging

From the close comments: duplicate 1

  • #81464 fix(cron): clarify RuntimeError when config.yaml is unreadable (#81420) · duplicate → #81426
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/81420.json
cluster/81420.md