liuhao1024 01ee312de6 fix(telegram): forward keepalive limits into fallback transport ... httpx ignores the client-level `limits` kwarg when a custom `transport` is supplied. The #31599 keepalive fix injected limits via `httpx_kwargs[limits]`, but the fallback-IP branch also passes a custom `TelegramFallbackTransport` — so the limits were silently discarded and the inner AsyncHTTPTransport instances ran with httpx defaults (keepalive_expiry=5.0), leaking CLOSE_WAIT fds. Pass the tuned limits directly into `TelegramFallbackTransport` via `transport_kwargs` so its inner transports honour keepalive_expiry. Only affects the fallback-IP branch; proxy and direct-DNS branches continue to use `_with_limits()` as before. Fixes #58790		2026-07-05 22:08:42 +05:30
..
__init__.py	refactor(gateway): migrate slack/dingtalk/whatsapp/matrix/feishu/telegram/wecom/email/sms adapters to bundled plugins	2026-06-20 10:26:45 -07:00
adapter.py	fix(telegram): forward keepalive limits into fallback transport	2026-07-05 22:08:42 +05:30
plugin.yaml	refactor(gateway): migrate slack/dingtalk/whatsapp/matrix/feishu/telegram/wecom/email/sms adapters to bundled plugins	2026-06-20 10:26:45 -07:00
telegram_ids.py	fix(telegram): accept @username chat_id in delivery paths (#13206)	2026-06-27 04:01:58 -07:00
telegram_network.py	fix(telegram): keep polling alive during transient bootstrap outages	2026-07-01 03:42:32 -07:00