Unexpected "could not canonicalize path" warnings in proxies when on a network drive

[brson]

Original report rust-lang/cargo#2990 (comment)

When running cargo run inside E:\hello_world cargo is printing warnings like

warning: could not canonicalize path: 'E:\hello_world'

That's pretty surprising since there's nothing interesting about that path.

[brson]

In the original report, drive E is a network drive. So it seems fs::canonicalize doesn't work on those.

Maybe we can detect when the drive is a network drive and not emit the warning, as a known case. Or maybe the warning is not worth printing at all.

[Scondo]

Same problem with ram drive... up to block of compilation.

[kinnison]

If you bypass rustup and run the compiler/cargo directly, are you able to compile/whatever? If so, then it's worth trying to bypass this in rustup, if the compiler or cargo also suffer then perhaps it'd be better as a bug against fs::canonicalize ?

[petrutlucian94]

I'm having the same issue with Docker Windows containers. In my case, the project dir is a volume exposed to the container (so it's basically a symlink pointing to something like \?\ContainerMappedDirectories<guid>).

I get the same warning and the build fails, unless I move the project files to a separate folder: http://paste.openstack.org/raw/751091/

From what I can tell, rustc cannot handle Windows symlinks.

LE: I think this issue has been duplicated A LOT of times against multiple repos, here are a few of them: rust-lang/rust#59117