Cairn
NousResearch/hermes-agent

Telegram duplicate messages after send timeouts or network errors

Cluster 3906 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
4items grouped
Known?
Yes. 4 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
0 issues and 1 PR.

The members center on Telegram messages being delivered more than once when a send times out or a NetworkError occurs after writing. One is a bug report citing stacked retry layers, and the other three are fix proposals to avoid resending in those cases.

Open issues0

No open issues.

Open PRs1

  • PR#64272fix(telegram): don't resend post-write NetworkError to avoid duplicate messages

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #3899 fix(telegram): prevent duplicate message delivery on send timeout · merged via another change → #5153
  • #3922 fix(telegram): prevent duplicate messages on send timeout · superseded by another PR
Closed issues · 1
  • Closed#3906bug: Telegram duplicate messages caused by stacked retry layers after send timeout
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.50: 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
gateway
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/3906.json
cluster/3906.md