You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I could reproduce this, it seems that this was a bug from the migration from wapm run to wasmer run: wapm run creates a file cowsay.cmd in ~/wapm_packages/.bin with the content:
@"wapm" run cowsay %*
When the command is executed, wasmer will be invoked with the path to the file, and for some reason it interprets the file path as a Url. This seems to only happen on Windows because Windows file paths start with C://, which gets parsed into a Url like http://. So it will try to fetch the file from the network and fail at that.
As a workaround wasmer run cowsay does work, even though there is some output that shouldn't happen.
fschutt
changed the title
Error: get_webc_bytes failed
wasmer run {url} interprets c:// file paths as URLs on Windows
Nov 24, 2022
3370: Fix wasmer run not interpreting URLs correctly + display fixes r=fschutt a=fschutt
Fixes#3366.
Fixes#3346.
Should land in the 3.0.2 release.
Co-authored-by: Felix Schütt <[email protected]>
Co-authored-by: Felix Schütt <[email protected]>
Describe the bug
I get the following error:
Steps to reproduce
Run above command on Windows
Expected behavior
Output from cowsay
Actual behavior
Error, see above
The text was updated successfully, but these errors were encountered: