-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
UPath failures on windows (must be absolute) with Subsystem #40
Comments
'/mnt/c/path/here' Also does not work, I see the documentation say that this typically does but I'm not sure why unless you were specifically running it under WSL which doesn't seem correct for x-platform. Looks like the assumptions made for this specifically tie across the library. |
This is by design. The README says the following:
Note the word "like", it doesn't say Zio does this only on WSL. You always use the unix path-style, even on Windows.
Do you get an exception? Does the program has access to the folder? When I tried the latest version on .NET Core 2.2.5 (x64) it's working fine: |
Yes, I cited that in my update; that's my fault.
It has access, but ultimately it appeared to be my fault here - sorry for the false message; I somehow missed a directory exist call that was using standard filesystem check vs. the Zio check. |
Facing with exactly same problem on Windows. I understand I must use a subPath formatted as Is there a simple way to convert " |
Line 225 in a563d0c
|
Thanks! |
I'm using a physical file system and a subsystem and if I'm using OSX it works perfectly fine, but on Windows it fails with 'Path 'c:/path/here' must be absolute'
var path = "c:/path/here/"
fs = new PhysicalFileSystem();
subfs = new SubFileSystem(fs, path);
This also fails on slower 'C:\path\here\'
I thought it was the trailing slash removal until I followed and noted that AssertAbsolute throws even with the trailing slash since the path does not start with / but c:/
The text was updated successfully, but these errors were encountered: