mirrors/hermes-agent
1
0
Fork 0
mirror of https://github.com/NousResearch/hermes-agent.git synced 2026-06-23 10:42:00 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

fix(telegram): keep chunk markers outside code fences

Browse source 
When truncate_message appends a (N/M) chunk indicator to a chunk that
had to close an in-progress fenced code block, the marker lands on the
closing fence line (``` \(1/2\) after MarkdownV2 escaping). Telegram
does not treat that as a clean closing fence and rejects the MarkdownV2,
falling back to plain text. Move the indicator onto its own line right
after the closing fence at all three legacy-send call sites.

Fixes #48517
This commit is contained in:
miha 2026-06-20 23:50:46 -07:00 • committed by Teknium
parent 5aec00f7a9
commit 796f618f99
2 changed files with 62 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

30
plugins/platforms/telegram/adapter.py
View file

@ -196,6 +196,24 @@ def _strip_mdv2(text: str) -> str:
return cleaned
_CHUNK_INDICATOR_ON_FENCE_RE = re.compile(
r'(?m)^``` (?P<indicator>(?:\\)?\(\d+/\d+(?:\\)?\))$'
)
def _separate_chunk_indicator_from_fence(text: str) -> str:
"""Move ``(N/M)`` chunk markers off Telegram code-fence lines.
``truncate_message()`` appends chunk indicators to the end of a chunk. When
the chunk had to close an in-progress fenced code block, that creates a
line like ````` \\(1/2\\)`` after MarkdownV2 escaping. Telegram does not
treat that as a clean closing fence, so it can reject MarkdownV2 and fall
back to plain text. Put the indicator on its own line immediately after the
closing fence.
"""
return _CHUNK_INDICATOR_ON_FENCE_RE.sub(r'```\n\g<indicator>', text)
# ---------------------------------------------------------------------------
# Markdown table → Telegram-friendly row groups
# ---------------------------------------------------------------------------
@ -2436,7 +2454,9 @@ class TelegramAdapter(BasePlatformAdapter):
# MarkdownV2-special parentheses so Telegram doesn't reject the
# chunk and fall back to plain text.
chunks = [
re.sub(r" \((\d+)/(\d+)\)$", r" \\(\1/\2\\)", chunk)
_separate_chunk_indicator_from_fence(
re.sub(r" \((\d+)/(\d+)\)$", r" \\(\1/\2\\)", chunk)
)
for chunk in chunks
]
@ -2910,7 +2930,9 @@ class TelegramAdapter(BasePlatformAdapter):
if finalize:
# Use format_message + parse_mode for the final chunk;
# mirror edit_message's main happy-path.
formatted = self.format_message(first_chunk)
formatted = _separate_chunk_indicator_from_fence(
self.format_message(first_chunk)
)
try:
await self._bot.edit_message_text(
chat_id=int(chat_id),
@ -2971,7 +2993,9 @@ class TelegramAdapter(BasePlatformAdapter):
for use_markdown in (True, False) if finalize else (False,):
try:
if use_markdown:
text = self.format_message(chunk)
text = _separate_chunk_indicator_from_fence(
self.format_message(chunk)
)
else:
# Plain attempt: on finalize the MarkdownV2 attempt
# failed, so degrade to clean stripped text, never