Cairn

Telegram streaming flood control partial/duplicate message fixes

NousResearch/hermes-agent · cluster 16668 · gateway

Data as of

Nothing open on GitHub. Fix merged in #23416. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #23416. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #23416. That is separate from the fix event.
Still open
Nothing open on GitHub.

A cluster of issues and fixes addressing Telegram gateway streaming edge cases, specifically around flood control leaving partial messages visible, sending duplicate final responses, and ensuring reliable delivery confirmation. The fixes cover suppressing duplicate replies, honoring retry-after delays, and cleaning up partial messages after fallback sends.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #23416 fix(gateway): delete partial message after fallback send on flood control (salvage of #17384)

    merged to main

    files: gateway/stream_consumer.py, scripts/release.py, tests/gateway/test_stream_consumer.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #17384 fix(gateway): delete partial message after fallback send on flood control · merged via another change → #23416
Closed issues · 2
  • Closed#16668Telegram streaming flood control can leave partial message and send duplicate final response
  • Closed#27942Telegram group edit streaming can leave final replies visibly unfinished
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
Merged PRs
#23416
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
10 May 2026

For your agent

The same facts, typed.

cluster/16668.json
cluster/16668.md