Stream: git-wasmtime

Topic: wasmtime / issue #7415 old CLI `--dir` arg clobbers new C...

view this post on Zulip Wasmtime GitHub notifications bot (Oct 30 2023 at 21:18):

ydnar added the bug label to Issue #7415.

view this post on Zulip Wasmtime GitHub notifications bot (Oct 30 2023 at 21:18):

ydnar opened issue #7415:

Thanks for releasing the compatibility shim in v14.0.3! I ran into an odd compatibility issue:

If wasmtime is run without WASMTIME_NEW_CLI=1, then --dir is always interpreted as a single value, and not HOST::GUEST. e.g.:

wasmtime run --dir ./::./ ...

Fails with:

Error: failed to open directory './::./'

view this post on Zulip Wasmtime GitHub notifications bot (Oct 30 2023 at 21:19):

ydnar edited issue #7415:

Thanks for releasing the compatibility shim in v14.0.3! I ran into an odd compatibility issue:

If wasmtime is run without WASMTIME_NEW_CLI=1, then --dir is always interpreted as a single value, and not HOST::GUEST, e.g.:

wasmtime run --dir ./::./ ...

Fails with:

Error: failed to open directory './::./'

view this post on Zulip Wasmtime GitHub notifications bot (Oct 30 2023 at 21:19):

ydnar edited issue #7415:

Thanks for releasing the compatibility shim in v14.0.3! I ran into an odd compatibility issue:

If wasmtime is run without WASMTIME_NEW_CLI=1, then --dir is always interpreted as a single value, and not HOST::GUEST:

wasmtime run --dir ./::./ ...

Fails with:

Error: failed to open directory './::./'

view this post on Zulip Wasmtime GitHub notifications bot (Oct 30 2023 at 21:35):

alexcrichton commented on issue #7415:

Thanks for the report, I've opened https://github.com/bytecodealliance/wasmtime/pull/7416 to fix the warning here and we can do a 14.0.4 release as well in a day or two to collect some more feedback.

I'll also confirm though that Wasmtime doesn't just fail with the error message above, it also prints the expected warning about the old-vs-new CLI, which is what I at least expected. Still something that's worth fixing because otherwise --dir-with-remapping behavior isn't actually able to be used without a warning or env var, which isn't great.

view this post on Zulip Wasmtime GitHub notifications bot (Oct 31 2023 at 20:04):

alexcrichton closed issue #7415:

Thanks for releasing the compatibility shim in v14.0.3! I ran into an odd compatibility issue:

If wasmtime is run without WASMTIME_NEW_CLI=1, then --dir is always interpreted as a single value, and not HOST::GUEST:

wasmtime run --dir ./::./ ...

Fails with:

Error: failed to open directory './::./'

view this post on Zulip Wasmtime GitHub notifications bot (Oct 31 2023 at 20:04):

alexcrichton commented on issue #7415:

Fixed in https://github.com/bytecodealliance/wasmtime/pull/7416, backported in https://github.com/bytecodealliance/wasmtime/pull/7421, and 14.0.4 will go out when https://github.com/bytecodealliance/wasmtime/pull/7431 is merged, so closing. Thanks again for the report!

Last updated: Nov 22 2024 at 16:03 UTC