Closed dicej closed 5 months ago
Thanks for merging this, @guybedford. Is there a chance we could publish a new release of the shim with this fix soonish? That would help unblock https://github.com/dotnet/runtimelab/pull/2614, which is where I encountered this issue.
Sure, I've pushed a 0.16.3.
When an application attempts to open a non-existent path such as
//foo/bar/baz
on Windows, Node generates an error of the form:Prior to this commit, that error would be re-thrown, causing Wasm execution to trap. Now we convert it to a "no-such-device" error instead.