Cairn
NousResearch/hermes-agent

Unicode/UTF-16 surrogate pair splitting bugs and fixes

Cluster 11466 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 2 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
Nothing open on GitHub.

Bug reports and fixes across Telegram messaging and desktop cron labels where text truncation incorrectly splits UTF-16 surrogate pairs, causing delivery failures or display issues.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #11522 fix(gateway): keep Telegram UTF-16 split points safe after natural break fallback · other → #11649, #11467
  • #11649 fix(telegram): prevent surrogate pair splitting in truncate_message · done elsewhere → #11467
Closed issues · 2
  • Closed#11466Telegram message splitting can slice UTF-16 surrogate pairs, causing delivery failures
  • Closed#11467Telegram message splitting can slice UTF-16 surrogate pairs, causing delivery failures
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
gateway
Closed issues
2
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/11466.json
cluster/11466.md