-
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
[browser] Fix encoding problem when publishing #82833
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsFixes #78953. For usernames with Unicode characters we had a problem because Window's .cmd scripts are not supporting Unicode (https://ss64.com/nt/chcp.html). Temporary files paths, e.g. "C:\Users\煉\AppData\Local\Temp\tmpC538.tmp" were passed to emcc with incorrect encoding and then could not be found in the file system which caused exceptions.
|
This needs a test in WBT. Instead of the username, the unicode characters can be in the project name. |
Failing on windows, and linux: runtime/src/tasks/AotCompilerTask/MonoAOTCompiler.cs Lines 1027 to 1028 in 9fd3ece
@maraf could you please take a look? |
This does similar operation on assembly names for WASI
|
We can replace the wasi one with FixupSymbolName which is more tested too. |
Thank you for a hint. Using the |
Stashing for later investigation:
|
These seem to be failing on CI too. |
Publish with relink tests on Blazor do not work.
emscripten-core/emscripten#17817. I will block these tests till emcc solves it. |
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.
Other than the comment, LGTM 👍
/backport to release/7.0 |
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/4435596854 |
@ilonatommy backporting to release/7.0 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Fixed https://github.com/dotnet/runtime/issues/78953.
Applying: New wbt publish test case: Unicode sign in project name.
Using index info to reconstruct a base tree...
A src/mono/wasm/Wasm.Build.Tests/BuildPublishTests.cs
Falling back to patching base and 3-way merge...
Applying: Removed duplicated, unused function + addressed @akoeplinger review.
Applying: Fix.
Applying: Revert AOT tests to fix them in a follow-up.
error: sha1 information is lacking or useless (src/mono/wasm/Wasm.Build.Tests/BuildPublishTests.cs).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0005 Revert AOT tests to fix them in a follow-up.
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@ilonatommy an error occurred while backporting to release/7.0, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
Fixes #78953.
For usernames with Unicode characters we had a problem because Window's .cmd scripts are not supporting Unicode (https://ss64.com/nt/chcp.html). Temporary files paths, e.g. "C:\Users\煉\AppData\Local\Temp\tmpC538.tmp" were passed to emcc with incorrect encoding and then could not be found in the file system which caused exceptions.
Out-of-scope:
runtime/src/mono/wasm/build/WasmApp.Native.targets
Line 475 in 99aa25f
Regressions with non-ASCII characters in path names emscripten-core/emscripten#17817