Stream: git-wasmtime

Topic: wasmtime / Issue #2650 wasi-common: UNC paths are not han...

Wasmtime GitHub notifications bot (Feb 09 2021 at 23:48):

pchickey opened Issue #2650.

Wasmtime GitHub notifications bot (Feb 09 2021 at 23:48):

pchickey labeled Issue #2650.

Wasmtime GitHub notifications bot (Feb 09 2021 at 23:50):

pchickey edited Issue #2650:

The following test executes correctly on a "normal" disk (C:\) on windows, but not on a network shared drive. @peterhuene determined that this is because UNC paths are not handled correctly in cap-std.
https://github.com/bytecodealliance/wasmtime/issues/2642#issuecomment-776293712

wasmtime main.wasm --dir .

fn main() -> std::io::Result<()> {
    let path = std::path::Path::new("dir.tmp");
    std::fs::create_dir(path)?;
    assert!(path.exists());
    Ok(())
}

Wasmtime GitHub notifications bot (Feb 27 2021 at 11:58):

whitequark commented on Issue #2650:

I've hit this while debugging a YoWASP application on a VirtualBox (mounted!) network drive. Makes that a bit annoying, although this is an admittedly obscure corner case.

Wasmtime GitHub notifications bot (Feb 27 2021 at 11:58):

whitequark edited a comment on Issue #2650:

I've hit this while debugging a YoWASP application on a VirtualBox (mounted!) network drive. Makes it a bit annoying to debug Windows applications, although this is an admittedly obscure corner case.

Wasmtime GitHub notifications bot (Mar 01 2021 at 16:13):

sunfishcode commented on Issue #2650:

I've started working on this in https://github.com/bytecodealliance/cap-std/pull/156, but I have a ways to go before I really understand how UNC paths work.

Wasmtime GitHub notifications bot (Mar 01 2021 at 16:21):

bjorn3 commented on Issue #2650:

https://docs.microsoft.com/en-us/dotnet/standard/io/file-path-formats and https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file have some documentation about the different kinds of paths on Windows.

Last updated: Dec 23 2024 at 13:07 UTC