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
2.1.300-preview2: Unable to use DotNetCliToolReference due to deps.json generation failure #2128
Comments
@dsplaisted please take a look ASAP. |
This looks like for this tool scenario, ResolvePackageAssets (which is new) is trying to write the assets cache to a location it doesn’t have write access to.
Tests missed this because the SDK folder isn’t write protected when the tests run.
|
@nguerrera @livarcocc Possible solutions:
Thoughts? |
This explains some test flakiness too, I think. |
I think opting in to a no-write-mode makes sense. @dsplaisted I can grab this if you're not already working on it. |
Fixed by #2134 |
|
There should be no performance impact to build. This changes a one time action to generate tool deps json but inner loop builds will still utilize the same package assets cache as before. There's an update to preview 2 going out with this fixed. There is unit test coverage added to prevent regression. |
There appears to be a regression in DotNetCliToolReference support.
Repro
On a clean mac, install the .NET Core CLI using the .pkg installer (not .tar.gz)
Create a new project via
dotnet new xunit
Run
dotnet xunit
Expected
Should launch xunit
Actual
The SDK fails to launch it with this error.
The real issue seems to be this:
The .pkg installer does not give write access to this path.
Workaround
Details
Using 2.1.300-preview2-008530
The text was updated successfully, but these errors were encountered: