Cairn
NousResearch/hermes-agent

Telegram gateway polling conflict recovery and freezing

Cluster 40691 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 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
Nothing open on GitHub.

One bug report describes the Telegram gateway freezing after polling conflict recovery, with passive routing stopping. Two pull requests, both referencing #40691, propose changes to recovery behavior, including dropping pending updates on conflict recovery. The titles alone do not show whether these changes address the reported freeze.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #40744 fix(telegram): drop pending updates on conflict recovery (#40691) · done elsewhere → d5ba374, #40691
  • #40827 fix(gateway): recover Telegram polling after conflicts (#40691) · done elsewhere → f038230, d5ba374, #40691
Closed issues · 1
  • Closed#40691[BUG] Telegram Gateway freezes after polling conflict recovery — passive routing stops working
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/40691.json
cluster/40691.md