fix(cli): use safe UTF-8 slicing for session IDs in lock command #35
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.
Summary
Fixes #5276 - Lock command session ID slicing panics on multi-byte UTF-8.
Problem
Session ID handling uses byte-based string slicing at 4 locations.
Solution
Replaced with safe slicing using .get() or char-aware methods.
Added a helper function
safe_char_prefixthat extracts string prefixes by character count rather than byte count, preventing panics on multi-byte UTF-8 characters.Changes
safe_char_prefixhelper function for UTF-8 safe slicingis_session_locked,run_list, andrun_checkfunctions