Time: 0:00
Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).
This bug belongs to the logic errors pattern
The wrong operator, an inverted condition, a formula the right way round but backwards.
What went wrong: String::truncate(n) expects n to be a byte offset that aligns with a UTF-8 character boundary. Truncating at byte index 7 splits the 4-byte globe emoji (bytes 6..10), causing a panic.
The fix: Truncate using character iteration: s.chars().take(max_chars).collect().
Remember: String::truncate operates on byte positions, not characters. Never pass character counts directly to truncate().
The pattern behind it: logic errors.
Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.
<iframe src="https://trybughunt.com/embed/c99e6f71-826a-46e9-bcf8-170862cca5b8" title="Debugging challenge: Truncate string on non-char boundary panics" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/c99e6f71-826a-46e9-bcf8-170862cca5b8">TryBugHunt</a></p>