Files
nanobot/nanobot
QQQ300kuaiandchengyongru 302015fde5 fix(telegram): keep lifecycle state consistent during polling recovery
- Fail outbound sends while the app is rebuilding instead of returning quietly, so ChannelManager retries and logs the failure instead of counting the message as delivered
- Close the bot's HTTPX pools during teardown: Application.shutdown() skips them when initialize() never finished, leaking one pool per startup retry
- Propagate terminal startup errors (rejected token, bad proxy, bound webhook port) and clear the running flag instead of retrying forever while the channel still reports itself healthy
- Restrict startup retries to NetworkError/TimedOut, the exceptions HTTPXRequest wraps every httpx failure into
- Scrub the rejected-token failure so PTB's token-bearing message never reaches the log
2026-08-18 00:41:57 +08:00
..
2026-08-08 21:10:34 +08:00
2026-07-13 13:11:46 +08:00
2026-02-01 07:36:42 +00:00