-
Notifications
You must be signed in to change notification settings - Fork 17
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
Update to wasi-cli@0.2.0 #43
Update to wasi-cli@0.2.0 #43
Conversation
I think the |
fb7b4fc
to
a0dfc28
Compare
Yeah, was trying to split out some changes to help isolate a wasm-encoder chage, but split out too much. |
@sunfishcode I've pushed some more WIT updates here as well as using the WIT bindgen bug fix at bytecodealliance/wit-bindgen#831 that was necessary to get this to build. The current failure is now that we use an empty world to build up the full virt world ( |
I've posted sunfishcode#1 as an update to this PR which updates the decoding process for the newly-encoded WIT format. |
I've updated the PR with @alexcrichton's fix, and can confirm the remaining bugs are now just in the deny and strip virt updates. Will try and push those shortly. |
It appears I missed updating all the signatures in virt_deny in bytecodealliance#43, so this commit updates them.
Update WASI-virt to wasi-cli@0.2.0-rc-2024-01-16. Several interfaces in wasi-sockets changed, so this updates the virtual-adapter accordingly.