Cairn
NousResearch/hermes-agent

Cron delivery timeout and HTTP config fixes

Cluster 38780 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

These items address a missing timeout in cron standalone delivery that can cause indefinite hangs, and a fix to reuse the gateway Telegram HTTP configuration in message sending.

Open issues0

No open issues.

Open PRs2

  • PR#38792fix(cron): add timeout to standalone delivery to prevent indefinite hang
  • PR#44996fix(send_message): reuse gateway Telegram HTTP config
Closed issues · 1
  • Closed#38780Cron standalone delivery has no timeout, so hung platform sends block job finalization
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
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/38780.json
cluster/38780.md