fix(tests): use explicit UTF-8 file I/O - #390
Merged
smaramwbc merged 2 commits intoSep 8, 2026
Merged
Conversation
Signed-off-by: eunwoo song <presentsong@naver.com>
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
2 participants
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.
Description
Makes all five identified source-file reads/writes explicitly UTF-8 so invariant and eval tooling no longer depends on the Windows locale codec.
Related Issue
Closes #350
Type of Change
Changes Made
encoding="utf-8"at every listed boundary.CONTRIBUTING.md.Testing
Test Commands Run
uv run ruff check . uv run pytest -qThe full run reached 1,334 passed and 5 skipped; only three live-stack smoke tests failed because the API service was intentionally not running. PostgreSQL-backed tests used the repository Docker database, which was stopped afterward.
Checklist