Uh oh!
There was an error while loading. Please reload this page.
[wasm] fix missing managed stack trace on managed exceptions marshaled to JS - #75678
Conversation
ghost
commented
Sep 15, 2022
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
|
pavelsavara
commented
Sep 15, 2022
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This comment was marked as outdated.
This comment was marked as outdated.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
kg
left a comment
There was a problem hiding this comment.
Looks fine other than the ManagedError inheritance question and toString
pavelsavara
commented
Sep 16, 2022
/azp run runtime-wasm |
|
Azure Pipelines successfully started running 1 pipeline(s). |
pavelsavara
commented
Sep 17, 2022
/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 128Please backport manually! |
When we display managed exception marshaled to JS as
ManagedErrorviatoStringwe only print:The fix makes it to print both managed and JS stack trace