Files
vibe-coding-cn/i18n/en/documents/03-practice/telegram-dev/Telegram Markdown Code Block Format Fix Log 2025-12-15.md
T
tukuaiai b264229f18 refactor(en): restructure en/documents to match zh structure
- Reorganize from 7 flat directories to 5 aggregated directories
- 00-fundamentals: core concepts, glue coding, methodology
- 01-getting-started: environment setup guides
- 02-methodology: tools, tutorials, development guides
- 03-practice: project examples (polymarket, telegram, fate-engine, etc.)
- 04-resources: templates, tools, external resources
- Remove duplicate files with underscore naming
- Add README.md for 00-fundamentals and 02-methodology
2025-12-19 02:02:06 +08:00

842 B

telegram Markdown Code Block Format Fix Log 2025-12-15

Problem

Error when sending message after chart generation:

❌ Chart generation failed: Can't parse entities: can't find end of the entity starting at byte offset 168

Cause

The Markdown code block format in the header message in bot.py is incorrect.

The original code used string concatenation, adding \n after ```, which prevented the Telegram Markdown parser from correctly recognizing the code block boundary:

# Incorrect usage
header = (
    "```\n"
    f"{filename}\n"
    "```\n"
)

Fix

Changed to use triple-quoted strings, ensuring ``` is on its own line:

# Correct usage
header = f"""Report in attachment

{filename} {ai_filename}

"""

Modified File

  • services/telegram-service/src/bot.py lines 293-308