Skip to content

fix(discord): use truncateUtf16Safe for deploy error body truncation#102525

Merged
steipete merged 2 commits into
openclaw:mainfrom
lsr911:fix/utf16-discord-deploy
Jul 9, 2026
Merged

fix(discord): use truncateUtf16Safe for deploy error body truncation#102525
steipete merged 2 commits into
openclaw:mainfrom
lsr911:fix/utf16-discord-deploy

Conversation

@lsr911

@lsr911 lsr911 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

What Problem This Solves

Discord deploy error logging truncates body text with naive .slice(0, maxLen), risking surrogate pair splitting in error messages.

Files Changed

File Change
extensions/discord/src/monitor/provider.deploy-errors.ts +1 import; .slice(0,N) → truncateUtf16Safe()

🤖 Generated with Claude Code

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

channel: discord Channel integration: discord merge-risk: 🚨 compatibility 🚨 May break existing users, config, migrations, defaults, or upgrade paths. P2 Normal backlog priority with limited blast radius. rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. size: XS status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. triage: needs-pr-context Candidate: external PR body lacks required problem context or evidence.