Discord component label UTF-16 boundary fix
Cluster 54968 · gateway. Data as of
Nothing open on GitHub. Fix merged in #60113 on 7 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #60113. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #60113. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items identify and address a bug where Discord component labels were being sliced by Unicode code points rather than UTF-16 code units. The work involves correcting the truncation logic to respect Discord's actual UTF-16 length limits.
Open issues0
Open PRs0
Fixes on record
-
#60113 fix(discord): bound component labels by UTF-16 units
files:
plugins/platforms/discord/adapter.py,tests/gateway/test_discord_clarify_buttons.py,tests/gateway/test_discord_model_picker.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#54969 fix(discord): bound component labels by UTF-16 units · merged via another change →
87be36c,#60113
Closed issues · 1
- Closed#54968Discord component labels use code-point slicing instead of UTF-16 limits
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.67: 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
- gateway
- Merged PRs
- #60113
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 7 Jul 2026