-
Notifications
You must be signed in to change notification settings - Fork 830
Fix cache path #15317
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
Fix cache path #15317
Conversation
Co-authored-by: Tomas Grosup <[email protected]>
Co-authored-by: Tomas Grosup <[email protected]>
psfinaki
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably would be nice to write/generate some unit tests for such things.
@psfinaki --- the reported issue, isn't an issue we have any control over. the NuGet.config file is not one we ever open, read , edit or anything else. It is a user file containing configuration specified by various applications. Indeed, it not having access to nuget.org is a normal, nuget scenario, and one in which we work fine. The error message even says what's wrong. It is certain that the corruption is not because of anything we do. |
There appears to be circumstances where Path.Combine treats elements not at the end of the list as extensions.
This issue here: #15294
contains this error:
The actual error is unrelated to this, however, the project was created in the wrong location:
It should have been:
It seems as if there are circumstance where:
combines the .packagemanagement as a file extension. I haven't been able to reproduce this locally. Perhaps it is locale related. This pr constructs the path more specifically