bytecodealliance
`wasm-compose` is deprecated
https://github.com/bytecodealliance/WASI-Virt/blob/4ef987e3eef808fdbc62ed4fa6c2de2f2b7f46ce/Cargo.toml#L70
is deprecated https://github.com/bytecodealliance/wasm-tools/commit/c034aafe906766f379ffad9b7447004a74b7364f in favor of wac https://github.com/bytecodealliance/wac about a year ago
Thanks for filing this @rosingrind ! Would you be up to updating the dependency?
Its pretty nontrivial to upgrade from wasm-compose to wac. Wasi-virt's s use of wasm-compose reflects that wasi-virt itself is not well maintained at the moment. Long story short, wasi-virt is not as useful as it should be in the Wasi 0.2 era, and the update to Wasi 0.3 should help make wasi-virt a lot more useful.
Until Wasi 0.3 is out and someone gets time to do a pretty comprehensive update of wasi-virt, its best to just consider it a very experimental project thats probably unsuitable for production use. As such, many dependencies will be very out-of-date.
Long story short, wasi-virt is not as useful as it should be in the Wasi 0.2 era, and the update to Wasi 0.3 should help make wasi-virt a lot more useful.
Just to clarify here, IIRC the main point was mismatches between imported and exported streams/wasi:io, right? It's not actually impossible to update the deps, correct? It's been a while since I've done the update.
Yes there are all the problems with virtualizing wasi:io in terms of performance (creates intermediate copies of all stream contents) and trust boundary (wasi-virt has to virtualize all io, must be totally trusted) to where its not considered practical or desirable for production use. But it still should be technically possible to update the deps