fix(telegram): redact bot tokens from poller errors

[gotnochill815-web]

Fixes #4769.

Summary

Prevent Telegram bot tokens from appearing in gateway logs or caller-visible errors when transient HTTP failures occur.

Changes

• Redact bot tokens from transient getUpdates exceptions before logging.
• Log the exception type separately for debugging.
• Redact bot tokens from Telegram HTTP error descriptions.
• Redact bot tokens from TelegramBotClient transport errors.
• Add regression tests covering exception, HTTP response, and client error paths.

Testing

• pytest -q gateway/tests/telegram/test_telegram_poller.py gateway/tests/telegram/test_telegram_client.py - 10 passed
• ruff check on changed files - passed
• git diff --check - passed

[github-actions]

Greptile code review

This repo uses Greptile for automated review. Before merge, aim for Confidence Score: 5/5 with zero unresolved review threads — see CONTRIBUTING.md.

Run a review — add a PR comment with:

@greptile review

Give it ~5-10 minutes (sometimes longer) for results, then fix feedback and re-trigger until you reach Confidence Score: 5/5.

Optional: automate with the greploop skill.

[greptile-apps]

Greptile Summary

The PR redacts Telegram bot tokens from poller exceptions, Telegram HTTP error descriptions, and client transport errors while retaining exception-type diagnostics.

• Applies the shared token-redaction helper before errors are logged or returned.
• Adds regression coverage for poller exception, HTTP response, and client transport-error paths.

Confidence Score: 4/5

The PR appears safe to merge, with only a non-blocking HTTP-status constant convention issue in a new test.

The changed runtime paths redact the configured token before logging or returning the targeted errors, and the only accepted concern is the use of a numeric HTTP status in regression coverage.

Files Needing Attention: gateway/tests/telegram/test_telegram_poller.py

Important Files Changed

Filename	Overview
gateway/transports/telegram/poller/client.py	Redacts the configured bot token from transport exception strings before they are logged or returned.
gateway/transports/telegram/poller/poller.py	Redacts tokens from transient exceptions and failed poll-response descriptions while logging the exception type separately.
gateway/tests/telegram/test_telegram_client.py	Adds focused coverage confirming client transport errors no longer expose the token.
gateway/tests/telegram/test_telegram_poller.py	Adds effective exception and HTTP-response redaction tests, but the new HTTP response fixture uses a hardcoded status code contrary to repository conventions.

_{Reviews (1): Last reviewed commit: "fix(telegram): redact bot tokens from po..." | Re-trigger Greptile}

[greptile-apps]

Hardcoded HTTP status code

The new response fixture uses the numeric status 500 instead of the repository-required named HTTPStatus constant, making the test less self-documenting and inconsistent with the established HTTP-status convention.

Context Used: AGENTS.md (source)

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[Devesh36]

Hey @gotnochill815-web someone else is already assigned to this issue. You have to take something else.