Test with non-Latin-1 Unicode characters on Windows #24270
Conversation
This file contains 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
github-actions
bot
added
the
awaiting-review
|
@bazel-io fork 8.0.0 |
meteorcloudy
approved these changes
Nov 11, 2024
meteorcloudy
added
awaiting-PR-merge
|
@fmeum could you please resolve the conflicts? Thanks |
|
@iancha1992 This is conflicting due to the rollback of the other Unicode commit, I'll rebase it when that one has been rolled forward. |
github-actions
bot
added
the
awaiting-review
CI runners have been updated in bazelbuild/continuous-integration@bd27193 to a Windows version that supports the approach taken in 7bb8d2b to start the JVM with UTF-8 as the system encoding.
fmeum
force-pushed
the
23859-unicode-everywhere
branch
from
0db034e
to
57771ba
Compare
|
@meteorcloudy Rebased onto master with the reland. |
Wyverald
removed
the
awaiting-review
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.
CI runners have been updated in bazelbuild/continuous-integration@bd27193 to a Windows version that supports the approach taken in 7bb8d2b to start the JVM with UTF-8 as the system encoding.