fix(telegram): persist private-chat topic sessions - #735
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing as superseded by #744, which merged the #734 fix into |
What
message_thread_idfor Telegram private chats(chat_id, None)TopicStateStore/newclearingWhy
Private-chat topic messages carry
message_thread_id, but_chat_session_key()rejected every threaded message. With forum topic management disabled, no other store handled those messages, so each follow-up started a fresh agent session.Fixes #734.
Testing
uv run pytest --ignore=tests/test_trigger_actions.py— 3134 passed, 1 skipped; 82.99% coverageuv run pytest --no-cov tests/test_trigger_actions.py -q— 31 passed_chat_session_key()behaviouruv run ruff check src testsuv run ruff format --check src testsuv lock --checkExisting baseline findings
tyremains informational in CI and reports pre-existing diagnostics; none are introduced in the changed lines.pip-auditreports the existingaiohttp 3.14.1advisories fromorigin/dev; this PR does not changeuv.lock.