Cairn
NousResearch/hermes-agent

Cron scheduler TypeError from max_turns string value

Cluster 82815 · 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 the cron scheduler crashes with a TypeError when max_turns is provided as a string or none in config. Fixes involve normalizing and coercing the value to an integer.

Open issues1

  • Issue#82815[Bug] Cron scheduler crashes with TypeError when config has max_turns: none

Open PRs2

  • PR#82729fix(cron): coerce string max_turns to int — prevent TypeError crash
  • PR#82845fix(cron): normalize string max_turns spellings to prevent TypeError (#82815)
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/82815.json
cluster/82815.md