Skip to content
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

Wasmer Freezes Up #71

Closed
cemalgnlts opened this issue Jun 17, 2023 · 2 comments
Closed

Wasmer Freezes Up #71

cemalgnlts opened this issue Jun 17, 2023 · 2 comments

Comments

@cemalgnlts
Copy link

Hi,

When I try in Wasmer I get no response:

@cemalgnlts ➜ /workspaces/codespaces-blank $ time wasmtime riscv-node.wasm
Welcome to Node.js v18.16.0.

Type ".help" for more information.
> .exit
.exit

real    0m13.176s
user    0m10.205s
sys     0m0.213s

@cemalgnlts ➜ /workspaces/codespaces-blank $ time wasmer run riscv-node.wasm 
^C
real    0m39.833s
user    0m0.087s
sys     0m0.143s

@cemalgnlts ➜ /workspaces/codespaces-blank $ 
@ktock
Copy link
Owner

ktock commented Jun 17, 2023

You need to pass --no-stdin to avoid blocking (e.g. wasmer out.wasm -- --no-stdin echo hello). AFAIK (as mentioned in https://github.com/ktock/container2wasm#wasi-runtimes-integration-status ), wasmer doesn't seem to support non-blocking stdin (i.e. select syscall on stdin) so this needs to be fixed for making stdio work on wasmer properly.

@cemalgnlts
Copy link
Author

Yes, it works now, thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants