Cairn
NousResearch/hermes-agent

Cron schedule re-parse round-trip idempotency fix

Cluster 89560 · cron. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs 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 2 PRs.

These issues and PRs address a bug where cron schedule parsing emits 'once at'/'once in' display strings that it cannot subsequently re-parse, causing errors on edit. The work focuses on making the serializer's output round-trip safely through parse_schedule.

Open issues1

  • Issue#89560cron: parse_schedule emits "once at"/"once in" displays it cannot re-parse (one-shot cron edit → ValueError/500)

Open PRs2

  • PR#89563fix(cron): re-parse the serializer's own once-at/once-in displays
  • PR#89568fix(cron): re-parse own display formats for round-trip idempotency

2 PRs closed without merging

From the close comments: duplicate 2

  • #89851 fix(cron): re-parse own "once at"/"once in" display strings (#89560) · duplicate → #89563
  • #99147 fix(cron): make parse_schedule idempotent over its own display strings · duplicate → #89563
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.40: 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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/89560.json
cluster/89560.md