-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[wasm] fix missing managed stack trace on managed exceptions marshaled to JS #75678
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
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsWhen we display managed exception marshaled to JS as
The fix makes use to print both managed and JS stack trace
|
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
This comment was marked as outdated.
This comment was marked as outdated.
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.
Looks fine other than the ManagedError inheritance question and toString
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
/backport to release/7.0-rc2 |
Started backporting to release/7.0-rc2: https://github.com/dotnet/runtime/actions/runs/3073338553 |
@pavelsavara backporting to release/7.0-rc2 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: fix missing managed stack trace on managed exceptions marshaled to JS
Using index info to reconstruct a base tree...
M src/libraries/System.Runtime.InteropServices.JavaScript/tests/System.Runtime.InteropServices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/JSImportExportTest.cs
M src/libraries/System.Runtime.InteropServices.JavaScript/tests/System.Runtime.InteropServices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/JavaScriptTestHelper.cs
M src/libraries/System.Runtime.InteropServices.JavaScript/tests/System.Runtime.InteropServices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/JavaScriptTestHelper.mjs
M src/mono/wasm/runtime/marshal-to-js.ts
M src/mono/wasm/runtime/marshal.ts
M src/mono/wasm/runtime/run.ts
M src/mono/wasm/runtime/types.ts
Falling back to patching base and 3-way merge...
Auto-merging src/mono/wasm/runtime/types.ts
Auto-merging src/mono/wasm/runtime/run.ts
CONFLICT (content): Merge conflict in src/mono/wasm/runtime/run.ts
Auto-merging src/mono/wasm/runtime/marshal.ts
Auto-merging src/mono/wasm/runtime/marshal-to-js.ts
Auto-merging src/libraries/System.Runtime.InteropServices.JavaScript/tests/System.Runtime.InteropServices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/JavaScriptTestHelper.mjs
Auto-merging src/libraries/System.Runtime.InteropServices.JavaScript/tests/System.Runtime.InteropServices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/JavaScriptTestHelper.cs
Auto-merging src/libraries/System.Runtime.InteropServices.JavaScript/tests/System.Runtime.InteropServices.JavaScript.UnitTests/System/Runtime/InteropServices/JavaScript/JSImportExportTest.cs
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 fix missing managed stack trace on managed exceptions marshaled to JS
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! |
When we display managed exception marshaled to JS as
ManagedError
viatoString
we only print:The fix makes it to print both managed and JS stack trace