Cairn
NousResearch/hermes-agent

Cron scheduling during gateway shutdown and interpreter finalization

Cluster 55924 · cron. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These items all concern the cron scheduler attempting to schedule work (futures, asyncio.run, pool.submit) while the gateway is shutting down or the interpreter is finalizing. One is a bug report of a "cannot schedule new futures" error during SIGTERM teardown, and two are fix proposals; the titles alone don't establish their outcome.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #55973 fix(cron): avoid scheduling work during shutdown · other
  • #55976 fix(cron): guard asyncio.run / pool.submit against interpreter finalization (#55924) · done elsewhere → 8aab8be
Closed issues · 1
  • Closed#55924[Bug]: cron scheduler can raise "cannot schedule new futures" during gateway SIGTERM teardown
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/55924.json
cluster/55924.md