Cairn
NousResearch/hermes-agent

Telegram streaming freeze from flood wait cap

Cluster 102402 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 1 PR.

These members address a bug where Telegram edit streaming freezes mid-text because a 5-second flood wait cap causes the bot to drop or skip edits during 18–35 second RetryAfter windows. The proposed fix involves waiting out the full flood window instead of capping it.

Open issues1

  • Issue#102402Telegram edit streaming freezes mid-text: 5s flood wait cap drops 18–35s RetryAfter edits

Open PRs1

  • PR#121791fix(telegram): wait out 18-35s edit flood windows instead of freezing the stream

1 PR closed without merging

From the close comments: partial fix 1

  • #102461 fix: Telegram edit streaming freezes mid-text: 5s flood wait cap drops 18–35s RetryAfter edits (#102402) · partial fix → #102461, #91969
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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/102402.json
cluster/102402.md