mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-07-31 19:16:29 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

more conservative to 120s

Browse source
This commit is contained in:
rob-maron 2026-07-30 17:26:40 -04:00 • committed by Teknium
parent dcd7a95704
commit 5932ec4552
1 changed files with 7 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

11
plugins/platforms/telegram/adapter.py
View file

@ -584,8 +584,9 @@ _POLLING_PROGRESS_TIMEOUT = 60.0
# Telegram transcodes an uploaded video before it answers sendVideo, so the
# wait for the response is unrelated to how fast the bytes went out and
# routinely exceeds the 20s read timeout the rest of the Bot API is tuned for.
# Only media sends take this longer budget.
_MEDIA_SEND_READ_TIMEOUT = 180.0
# Only media sends take this longer budget; ordinary calls keep the short one
# so a dead request is still noticed quickly.
_MEDIA_SEND_READ_TIMEOUT = 120.0
_POLLING_GENERATION_CONTEXT: ContextVar[Optional[int]] = ContextVar(
"telegram_polling_generation", default=None
)
@ -3672,9 +3673,11 @@ class TelegramAdapter(BasePlatformAdapter):
# Not a duplicate of write_timeout: PTB routes any request
# carrying files to media_write_timeout instead, so the line
# above never applied to an upload and every upload was pinned
# to PTB's own 20s default.
# to PTB's own 20s default. 120s covers a 50MB video on a
# ~4Mbps uplink; going higher only lengthens how long a dead
# socket takes to report itself.
"media_write_timeout": _env_float(
"HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT", 300.0
"HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT", 120.0
),
}