fix(discord): keep thread title prompts UTF-16 safe#101551
Merged
Merged
Conversation
Co-authored-by: Alix-007 <[email protected]>
openclaw-barnacle
Bot
added
channel: discord
Contributor
Author
|
Land-ready review complete at exact head
|
Contributor
Author
|
Merged via squash.
|
This was referenced Jul 7, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 8, 2026
Co-authored-by: Alix-007 <[email protected]>
giodl73-repo
pushed a commit
to giodl73-repo/openclaw
that referenced
this pull request
Jul 8, 2026
Co-authored-by: Alix-007 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related: #101307
What Problem This Solves
Fixes an issue where Discord users generating automatic thread titles could send malformed prompt text when a message, channel name, or channel description hit its character cap in the middle of an emoji.
Why This Change Was Made
All three bounded prompt fields now use OpenClaw's shared UTF-16-safe truncation helper. The formatter remains private, and the regression exercises the actual title-generation completion path rather than adding a test-only production export.
The original contributor branch became ancestry-corrupted and could not be rewritten through GitHub's maintainer-edit path, so this clean maintainer branch preserves the contributor's authorship via
Co-authored-by.User Impact
Discord thread-title generation keeps the same limits and ellipsis behavior while avoiding dangling UTF-16 surrogate halves in model prompts.
Evidence
generateThreadTitlewith split-surrogate boundaries in message text, channel name, and channel description, then inspects the real completion prompt.oxfmt --checkfor both touched files: passed.git diff --check: passed.