Cairn
NousResearch/hermes-agent

Telegram media upload write timeout config wiring

Cluster 21757 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
8items grouped
Known?
Yes. 8 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 5 PRs 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 issues and PRs all concern a missing or unset media_write_timeout parameter in the Telegram/PTB integration, causing large file uploads to hit PTB's 20-second default regardless of any configured environment variable. The work involves exposing and correctly wiring HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT through to PTB's HTTPXRequest configuration.

Open issues1

  • Issue#62936[Bug]: Telegram uploads >~15 MB always fail with TimedOut — HERMES_TELEGRAM_HTTP_WRITE_TIMEOUT has no effect on media uploads (PTB media_write_timeout never set)

Open PRs1

  • PR#69984fix(telegram): align standalone media upload timeout with gateway

5 PRs closed without merging

From the close comments: duplicate 2 · superseded by another PR 1 · other 2

  • #21766 fix(telegram): add media_write_timeout to gateway HTTPXRequest config · other
  • #21777 fix(gateway): wire HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT to PTB so large media uploads stop hitting the 20s default · other → 5600105, #21757, #62941
  • #27473 feat(telegram): add media_write_timeout for large file uploads · duplicate → #21777
  • #46493 feat(telegram): set media_write_timeout when python-telegram-bot supports it · superseded by another PR → #21777, #21757
  • #62941 fix(telegram): add HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT for large file uploads · duplicate → #21777, #62941
Closed issues · 1
  • Closed#21757Gateway Telegram adapter ignores HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT — large media uploads time out at PTB's 20s default
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.23: 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
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/21757.json
cluster/21757.md