Open juljaeg opened 11 months ago
Is there an ETA for this since the first reports are ~2 years old? Will this be covered with WSL Support? Especially in large repositories Fork would be helpful now 😕
This is a problem in .Net framework, not in Fork.
Is there an ETA for this since the first reports are ~2 years old?
No
I am not sure if this is completly on the framework, as it is made to run in Windows and also acts like it. Admittedly Fork is as well build for Windows and not for WSL Hybrid shenanigans 😥 So I can understand when you say it is an unsupported scenario.
There are ways to address this I think tho. Tho they are either "hacky" (if path starts with something wsl then skip xy - not sure if that even works) or rather ridiculously complex (switching to .NET Core and using the remote backend approach from e.g. VS Code and JetBrains IDEs). Not sure if you got anything like that planned anyway.
So I guess we can close this issue as won't fix or should it stay open?
Hi,
I have a large repository. When I open that repo in fork in WSL it crashes. When I open the same repository on Windows itself I get an error regarding files in the repository containing invalid characters which are not supported in file/directory names on windows - which is right. In Linux those characters are allowed tho. Is it possible to skip or validate the paths differently when the repository is in WSL?
I know there is some WSL stuff going on but did not want to spam the thread there. Working with the same repo in WSL over e.g. VS Code with WSL remote or plain git cli works fine.
Stacktrace from event viewer (when crashing when in WSL):