Skip to content

fix(telegram): avoid conflicting get_updates proxy config#200

Merged
frostming merged 2 commits into
bubbuild:mainfrom
iodone:fix/telegram-proxy-builder-conflict
May 7, 2026
Merged

fix(telegram): avoid conflicting get_updates proxy config#200
frostming merged 2 commits into
bubbuild:mainfrom
iodone:fix/telegram-proxy-builder-conflict

Conversation

@iodone
Copy link
Copy Markdown
Contributor

@iodone iodone commented May 6, 2026

Summary

  • avoid combining get_updates_request(...) with get_updates_proxy(...)
  • pass the proxy directly into HTTPXRequest(...) for the polling request
  • add a regression test covering the proxy-enabled startup path

Why

python-telegram-bot raises a RuntimeError when get_updates_request is already set and get_updates_proxy is then configured on the same builder. This caused TelegramChannel.start() to fail during gateway startup when BUB_TELEGRAM_PROXY was set.

Verification

  • uv run pytest tests/test_channels.py -q

@frostming frostming merged commit 12be69d into bubbuild:main May 7, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants