Timezone-aware scheduling and time functions

NousResearch/hermes-agent · cluster 26549 · cron

Data as of

2 open items. No fix on record.

The short answer

2open issues
0open PRs
2items grouped
Known?
Yes. 2 related items grouped here, 0 issues already closed.
Fix event
No merged or attempted fix PR is on record for this cluster.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 0 PRs. Broad area: open items may be separate problems.

These members address adding timezone and locale support to cron job scheduling and time-related functions such as now(). The work spans feature requests and a fix for making time handling timezone-aware across multiple contexts.

Open issues2

  • Issue#26549Per-job timezone for cron schedules
  • Issue#33036Feature Request: Locale-aware cron scheduling — jobs that follow the user's timezone

Open PRs0

No open pull requests.

How this cluster was grouped
  • Link evidence (automated judgement only): no structural link between members; the grouping rests entirely on an automated relevance judgement over their text.
  • Read the members yourself before treating them as one problem.
  • Pairwise link density 0.36: 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.