Telegram MarkdownV2 chunk indicator escaping fixes
NousResearch/hermes-agent · cluster 74004 · agent
Data as of
5 open items. Fix attempted, not merged.
The short answer
1open issue
4open PRs
7items grouped
- Known?
- Yes. 7 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 4 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMultiple issues and fixes addressing MarkdownV2 formatting problems in Telegram's chunked message sending path, specifically around escaping reserved characters in chunk indicators and handling message overflow.
Open issues1
- Issue#74004[Bug]: Telegram Markdown formatting silently lost on chunked messages in standalone send path (_send_telegram)
Open PRs4
- PR#74040fix(telegram): escape MarkdownV2 reserved parens in chunk indicators (#74004)
- PR#74055fix(tools): escape MarkdownV2 chunk indicators
- PR#74107fix(telegram): escape chunk indicator parentheses in _send_telegram standalone path
- PR#126100fix(telegram): escape chunk indicators in the standalone send path (salvage #74040)
2 PRs closed without merging
From the close comments: stale or abandoned 1 · superseded by another PR 1
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.29: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Closed issues
- 0
- Attempts
- 2 PRs closed without merging