Skip to content
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

The restore command should not write any assets itself, everything should be written when the RestoreResult is committed #3261

Merged
merged 5 commits into from
Feb 26, 2020

Conversation

nkolev92
Copy link
Member

@nkolev92 nkolev92 commented Feb 24, 2020

Bug

Fixes: NuGet/Home#8793
Regression: Yes

  • Last working version: 5.4
  • How are we preventing it in future: We have a test now

Fix

Details: When restore is run without a commit, it should not generate any assets.
This caused a permissions problem with the resolver on linux where, because the temp folder is machine-wide while the restore process was running without admin permissions.

Note that this is a regression and ideally is reviewed with high priority :)

Testing/Validation

Tests Added: Yes
Reason for not adding tests:
Validation:

@nkolev92 nkolev92 changed the title Dev nkolev92 restore result cleanup The restore command should not write any assets itself, everything should be written when the RestoreResult is committed Feb 24, 2020
@nkolev92
Copy link
Member Author

Update: This is the right fix long term and will go into 5.6 eventually.
I'll create a new PR with a smaller footprint for 5.5.

@nkolev92 nkolev92 force-pushed the dev-nkolev92-restoreResultCleanup branch from fb604d7 to c258545 Compare February 26, 2020 00:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Perf: DG Spec for unloaded project scenarios should not be written in preview restores
4 participants