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

fix: Fix async runtime mismatch in virtual "wasmer run" command #4272

Merged
merged 1 commit into from
Oct 26, 2023

Conversation

theduke
Copy link
Contributor

@theduke theduke commented Oct 23, 2023

The virtual "wasmer run" command available in wasix was switched to a
inline waker for resolving the future, but it calls
BinaryPackage::from_registry, which needs to run in a tokio runtime, due
to doing web requests for package retrieval.

Easily fixed by delegating to the main runtime.

Closes #4269

The virtual "wasmer run" command available in wasix was switched to a
inline waker for resolving the future, but it calls
BinaryPackage::from_registry, which needs to run in a tokio runtime, due
to doing web requests for package retrieval.

Easily fixed by delegating to the main runtime.

Closes #4269
@theduke theduke force-pushed the issue-4269-fix-virtual-wasmer-run-command branch from 535abe3 to 4689b2f Compare October 23, 2023 12:29
@syrusakbary syrusakbary disabled auto-merge October 26, 2023 01:29
@syrusakbary syrusakbary merged commit 28bb3cb into master Oct 26, 2023
51 of 53 checks passed
@syrusakbary syrusakbary deleted the issue-4269-fix-virtual-wasmer-run-command branch October 26, 2023 01:29
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

Successfully merging this pull request may close these issues.

Unable to use wasmer run ... inside a running WASIX program
3 participants