-
Notifications
You must be signed in to change notification settings - Fork 587
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
Running into PathTooLongExceptions with our project because we have node_modules. #537
Comments
@colinbull started to work on a fix - see colinbull@bc52adb would this help? |
I don't no it might but why plough through the whole node_modules directory when looking for nuget.exe? |
I added a small quickfix. If the path scanning fails we just return the default path. So you can override it with your concrete nuget path. Is this OK? |
Yes it is! Thanks, I was just looking through the code at the fix you did for something similar here: https://github.com/curit/FAKE/blob/master/src/app/FakeLib/Globbing/FileSystem.fs#L147 |
released with 3.4.1 |
Very impressive @forki fixed within the hour 👍 |
Is it possible there is a regression on this bug ? FakePath: C:\dev\ppp\source\gppp\packages\FAKE\tools\FakeLib.dll .\packages\FAKE\tools\FAKE.exe .\build.fsx For help type #help;;
System.IO.PathTooLongException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. |
Its failing when looking for the packages.config: let nugetPath = EnvironmentHelper.environVarOrDefault "nugetPath" @"C:\tools\nuget\nuget.exe" |
I started working on a fix for this mentioned above, but there is is lots of ins-and-outs when dealing with a long paths. It is probably just best avoided - I couldn't really get it working smoothly which is why I dropped it. |
Would it be an idea to add a flag somewhere where you can say I don't care about paths that are too long when globbing?
Or maybe have a list of directories that should be ignored when globbing.
The text was updated successfully, but these errors were encountered: