-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use multibyte character path for bundle_probe #44466
Conversation
Tagging subscribers to this area: @vitek-karas, @agocke Issue meta data
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - let's wait for @janvorli to take a second look
Internal to CoreCLR; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
The win x86 leg was failing due to something that looks like a bug in xunit (xunit code modifying a collection while it was being iterated). I am re-running this leg. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also make sure the single-file doc in dotnet/designs reflects this change.
Edit: Actually, apparently the design doc does have char
, but the implementation didn't match.
When runtime repo itself is cloned in a path containing multibyte character, I found two issues. Steps to repro (using three-bytes characters): $ git clone https://github.com/dotnet/runtime runtime-ⒾⓇⓇⒺⒼⓊⓁⒶⓇ␣ⓉⒺⓍⓉ
$ cd runtime-ⒾⓇⓇⒺⒼⓊⓁⒶⓇ␣ⓉⒺⓍⓉ
$ ./build.sh -c Release
$ ./build.sh Host.Tests -c Release -test
With these two patches, full runtime repo build succeeded and all installer tests passed on macOS. It seems like there are other |
Thanks a lot @am11 ! |
Fixes #44098.