Cairn
NousResearch/hermes-agent

Telegram standalone send read timeout fix

Cluster 133164 · agent. 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.

A bug was identified where standalone Telegram sends use a short default read timeout, causing false timeout errors and duplicate messages on retry. Related entries address giving these sends a configurable or longer read timeout.

Open issues1

  • Issue#133164[Bug]: standalone Telegram send (hermes send) uses PTB default read_timeout=5s — media sends report 'Timed out' although delivered (duplicates on retry)

Open PRs1

  • PR#135661fix(tools): give standalone telegram sends a real read timeout

1 PR closed without merging

From the close comments: closed without comment 1

  • #135625 fix(tools): give standalone telegram sends a real read timeout · 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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/133164.json
cluster/133164.md