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.

Sign up for GitHub

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

Jump to bottom

Wasmer stdout is not good #3814

Closed
syrusakbary opened this issue Apr 22, 2023 · 3 comments · Fixed by #3820
Closed

Wasmer stdout is not good #3814

syrusakbary opened this issue Apr 22, 2023 · 3 comments · Fixed by #3820
Assignees
@theduke @ptitSeb
Milestone
v3.3

Comments

@syrusakbary
Copy link
Member

Try to run spidermonkey js.wasm: https://firefoxci.taskcluster-artifacts.net/Wl0gB9DqTUOyBSenX32lXg/0/public/build/js.wasm

$ wasmer run js.wasm
1+1 // <---- This is what you input in the shell, and you press enter
js> 2

It should be:

$ wasmer run js.wasm
js> 1+1 // <---- This is what you input in the shell, and you press enter
2
js>
@syrusakbary syrusakbary added this to the v3.3 milestone Apr 22, 2023
@syrusakbary
Copy link
Member Author

You can check with other runtimes how it actually runs properly

@ktock
Copy link

ktock commented Apr 22, 2023

Maybe related to #3790 ?

@syrusakbary
Copy link
Member Author

Probably!

@ibrahim-akrab ibrahim-akrab mentioned this issue Apr 24, 2023
Closed
@mucinoab mucinoab mentioned this issue Apr 25, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@theduke theduke

@ptitSeb ptitSeb

Labels
None yet
Projects
None yet
Milestone
v3.3
Development

Successfully merging a pull request may close this issue.

fd_write: Flush on every write to a file mucinoab/wasmer
4 participants
@syrusakbary @theduke @ptitSeb @ktock