Skip to content

fix(telegram): refresh topic binding after session split#20486

Closed
LeonSGP43 wants to merge 1 commit into
NousResearch:mainfrom
LeonSGP43:fix/telegram-topic-binding-session-split
Closed

fix(telegram): refresh topic binding after session split#20486
LeonSGP43 wants to merge 1 commit into
NousResearch:mainfrom
LeonSGP43:fix/telegram-topic-binding-session-split

Conversation

@LeonSGP43

Copy link
Copy Markdown
Contributor

Summary

  • refresh Telegram DM topic bindings when context compression rotates a gateway session id
  • keep the existing SessionStore rollover behavior for all platforms
  • add a regression test for topic bindings after compression-created session splits

Closes #20470

Verification

  • scripts/run_tests.sh tests/gateway/test_telegram_topic_mode.py

Non-goals

  • does not change Telegram topic creation, /new handling, or existing session switching semantics
  • does not attempt to repair historical stale bindings automatically

@alt-glitch alt-glitch added type/bug Something isn't working P1 High — major feature broken, no workaround comp/gateway Gateway runner, session dispatch, delivery platform/telegram Telegram bot adapter labels May 6, 2026
@alt-glitch

Copy link
Copy Markdown
Collaborator

Competing fix for #20470 — see also #20485 which takes an inline approach without extracting a helper method.

@LeonSGP43

Copy link
Copy Markdown
Contributor Author

Closing this duplicate for #20470. PR #20485 already covers the same Telegram DM topic binding refresh after compression split, and keeping both open creates unnecessary overlap for maintainers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/gateway Gateway runner, session dispatch, delivery P1 High — major feature broken, no workaround platform/telegram Telegram bot adapter type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug] Telegram DM topic binding not refreshed after compression-induced session split — causes preflight compression loop

2 participants