Wasmtime GitHub notifications bot (Mar 26 2024 at 09:44): Wasmtime GitHub notifications bot (Mar 26 2024 at 09:44):jeffparsons added the bug label to Issue #8241.
Wasmtime GitHub notifications bot (Mar 26 2024 at 09:44):jeffparsons opened issue #8241:
On Wasmtime 18, I had
wit/deps/cli,wit/deps/clocks, etc. as symlinks to vendored WASI wit files.After upgrading to Wasmtime 19, this same structure results in the error:
failed to resolve directory while parsing WIT for path
Replacing the symlinks with copies of the target directory resolves the issue.
I'm not sure if this will be regarded as a bug, but I don't see why symlinks shouldn't be supported here. I guess it was just an accidental regression with recent bindgen changes? :man_shrugging:
Wasmtime GitHub notifications bot (Mar 26 2024 at 14:18):alexcrichton commented on issue #8241:
Thanks for the report! I think that this is fixed by https://github.com/bytecodealliance/wasm-tools/pull/1437, so I'll get new versions of those crates published so we can pull them in here.
Wasmtime GitHub notifications bot (Mar 26 2024 at 17:39):alexcrichton closed issue #8241:
On Wasmtime 18, I had
wit/deps/cli,wit/deps/clocks, etc. as symlinks to vendored WASI wit files.After upgrading to Wasmtime 19, this same structure results in the error:
failed to resolve directory while parsing WIT for path
Replacing the symlinks with copies of the target directory resolves the issue.
I'm not sure if this will be regarded as a bug, but I don't see why symlinks shouldn't be supported here. I guess it was just an accidental regression with recent bindgen changes? :man_shrugging:
Last updated: Nov 22 2024 at 16:03 UTC