{"repo":"NousResearch/hermes-agent","public_id":"82920","display_label":"Telegram transport pool reset and connection leak","summary":"These items concern a bug where Telegram's fallback-IP transport bypasses HTTP connection limits causing CLOSE_WAIT socket leaks, and associated corrections to reset the primary transport pool when it enters an error state.","subsystem":null,"counts":{"members":3,"open_issues":0,"open_issues_distinct":0,"open_prs":0,"closed_issues":1,"merged_prs":1,"attempt_prs":1},"landed_fix":{"status":"merged_to_main","basis":"structural","pr":83044,"merged_at":"2026-08-10T08:16:48+00:00"},"resolution":{"state":"resolved","by":"pr-83044"},"freshness":{"state":"verified","last_verified_at":"2026-08-10T08:16:48+00:00","is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[{"issue_number":82920,"pr_number":83044,"tier":"verified","basis":"closing_ref","confidence":0.95,"recoverable_from_timeline":true,"pr_merged_at":"2026-08-10T08:16:48+00:00"}],"members":[{"kind":"issue","number":82920,"title":"[Bug]: Telegram fallback-IP transport bypasses platform_httpx_limits() — CLOSE_WAIT leak (~18/hr) → EMFILE when no fallback_ips are configured","url":null,"state":"closed"},{"kind":"pr","number":83001,"title":"fix(telegram): reset failed primary transport pool","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#83044","number":83044}],"category":"merged_via","implication":"superseded"},"merged":false},{"kind":"pr","number":83044,"title":"fix(telegram): reset failed primary transport pool","url":null,"state":"merged","close_reason":{"category":"merged"},"merged":true,"is_fix_pr":true,"fix_tier":"verified","files_changed":["plugins/platforms/telegram/telegram_network.py","tests/gateway/test_telegram_closewait_limits_31599.py","tests/gateway/test_telegram_fallback_pool_release_71593.py"]}],"trust":{"default_tier":"verified","includes_suggested":false}}