-
Notifications
You must be signed in to change notification settings - Fork 903
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
Handle null items better #853
Comments
Greetings- I'm seeing something similar while trying to do
|
so I was doing It executed fine now. |
ferventcoder
added a commit
that referenced
this issue
Jul 24, 2016
When a path is empty or null, handle it with either better error messaging or work around the issue. - Do not allow combining paths when the left side is null. - When attempting to get files from a directory, if the directory value is empty, do not perform the search. - When splitting strings, attempt to always remove empty entries. - Check null or empty for strings
ferventcoder
added a commit
that referenced
this issue
Jul 24, 2016
* stable: (maint) Skip log PowerShell resource assembly failures (GH-871) Fix - Uninstall zip: Path is empty string (maint) remove unused import (GH-854) Reset Exit Code between package runs (GH-852) Bump up the default log sizes (GH-867) NuGet.Core Errors Exit Code 1 (GH-853) Handle null values better (GH-836) Fix - Use 32 bit 7zip (GH-847) Tab Completion Enhancements (GH-857) Fix - Sometimes paths contain null chars
ferventcoder
added a commit
that referenced
this issue
Aug 10, 2016
Do not remove empty entries in the case of prompt for choice, which is determining if a string contains `&` so it can build the labels properly. This is a partial reversion of what was introduced by 401335b.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are some errors like
That tend to crop up when things do not install correctly. Handle these better.
The text was updated successfully, but these errors were encountered: