fix: replace garbled mojibake characters with clean ASCII in comments#29
Open
57388sp wants to merge 2 commits into
Open
fix: replace garbled mojibake characters with clean ASCII in comments#2957388sp wants to merge 2 commits into
57388sp wants to merge 2 commits into
Conversation
|
Test Report missing or unfilled. This PR touches This is a soft gate - your CI checks are unaffected - but reviewers will not approve until the report is filled in. |
hvinn
approved these changes
May 12, 2026
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
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.
Several Python source files contained mojibake characters — Windows CP1252
bytes misread as UTF-8 — in docstrings and comments. This was likely
introduced when files were edited in a non-UTF-8 editor.
Changes:
—with-(em-dash mangled)…with...(ellipsis mangled)→with->(arrow mangled)✓with[OK](checkmark mangled)(
AGGR_NAME,ONTAP_PASS,CLUSTER_PASS, node IPs) — these shouldnever be committed; users set them via env vars or --env-file
No logic changes. Tests: 154/154 pass. Ruff: clean.