Cairn
NousResearch/hermes-agent

Cron transport receipt persistence with delivery outcomes

Cluster 70945 · cron. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 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 0 PRs.

These members concern adding persistence of transport receipts in the cron system, with a focus on conservative handling of delivery outcomes such as not treating timeouts as successful delivery.

Open issues1

  • Issue#70945Cron: persist conservative transport receipts without treating timeouts as delivery

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: closed without comment 1 · done elsewhere 1

  • #71086 feat(cron): persist transport receipts with delivery outcome contract (#70945) · done elsewhere
  • #93009 feat(cron): persist conservative transport receipts · closed without comment
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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/70945.json
cluster/70945.md