Fix UnicodeDecodeError with non-UTF-8 filenames in SSH operations
#386
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.
Fix
UnicodeDecodeErrorwith non-UTF-8 filenames in SSH operationsThis PR fixes a critical bug where migrations fail with
UnicodeDecodeErrorwhen source systems contain files or directories with non-UTF-8 characters in
their names.
The fix centralizes UTF-8 decoding with error handling in
exec_ssh_cmd(),which now returns decoded strings with
errors='replace'instead of raw bytes.Invalid UTF-8 sequences are replaced with the
�character, allowing migrationsto continue while logging warnings for monitoring.
Changes:
exec_ssh_cmd()to return strings with safe decodinglist_ssh_dir()for encoding errors.decode()calls on command execution results (15 locations)Impact: