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 wasm publish validation #3473

Merged
merged 1 commit into from
Jan 11, 2023
Merged

Fix wasm publish validation #3473

merged 1 commit into from
Jan 11, 2023

Conversation

syrusakbary
Copy link
Member

Follow up from this PR: wasmerio/wapm-cli#305

Copy link
Contributor

@Michael-F-Bryan Michael-F-Bryan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me 👍

After talking with @syrusakbary this evening, I agree with the idea of enabling all WebAssembly features while validating.

One option is to get the flags from wasmer::Features::default() instead of hard-coding them, but that would enforce validation using the current Wasmer defaults. We are actually trying to validate that each atom would be runnable by the end runner, though, and there is no way to know which features a runner would enable or disable (something that's essentially impossible to know).

Given that, I agree with being "optimistic" and allowing all WebAssembly features when validating packages before publishing - it's more of a sanity check, anyway.

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.

2 participants