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

The wasmer run command doesn't show any output when starting #3981

Closed
Michael-F-Bryan opened this issue Jun 9, 2023 · 0 comments · Fixed by #3985
Closed

The wasmer run command doesn't show any output when starting #3981

Michael-F-Bryan opened this issue Jun 9, 2023 · 0 comments · Fixed by #3985
Assignees
@Michael-F-Bryan
Labels
priority-medium Medium priority issue
Milestone
v4.0

Comments

@Michael-F-Bryan
Copy link
Contributor

Describe the bug

When running the wasmer run command on the latest master (f93f083) there is a 1-second delay on startup. The delay itself has its own ticket (#3962), but this highlights that the wasmer run command needs to show some sort of interactive output so users don't get impatient and think it has locked up.

The messages I'm thinking we should show are:

  • Loading the initial target (e.g. a *.webc or *.wasm on disk or something remote) (spinner)
  • The resolution stage (spinner)
  • Packages as they are being downloaded from WAPM or the internet (progress bar)
  • Initializing the WASI environment & runner (spinner)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Michael-F-Bryan Michael-F-Bryan

Labels
priority-medium Medium priority issue
Projects
None yet
Milestone
v4.0
Development

Successfully merging a pull request may close this issue.

Display human-friendly progress when starting wasmer run wasmerio/wasmer
2 participants
@ptitSeb @Michael-F-Bryan