fix: correct sparse VHD command to include true#13512
fix: correct sparse VHD command to include true#13512benhillis merged 5 commits intomicrosoft:masterfrom
true#13512Conversation
|
@microsoft-github-policy-service agree |
benhillis
left a comment
There was a problem hiding this comment.
This is the only file you need to modify, the rest are auto-generated.
|
Thanks for the review!
Sorry if i get your comment wrong - I suppose you mean only |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
i see the Azure workflow fails. now i understand how the translation automation works, i can debug and test locally. just a moment before i push the fix |
| wsl.exe --manage <DistributionName> --set-sparse --allow-unsafe</value> | ||
| <comment>{Locked="--manage "}{Locked="--set-sparse "}{Locked="--allow-unsafe"}Command line arguments, file names and string inserts should not be translated</comment> | ||
| wsl.exe --manage <DistributionName> --set-sparse true --allow-unsafe</value> | ||
| <comment>{Locked="--manage "}{Locked="--set-sparse true "}{Locked="--allow-unsafe"}Command line arguments, file names and string inserts should not be translated</comment> |
There was a problem hiding this comment.
Please run: python tools\devops\validate-localization.py --fix locally to format this, this should unblock the CI
There was a problem hiding this comment.
sorry for the misunderstanding in the Locked syntax. the issue should now be fixed by running the script as you suggested
There was a problem hiding this comment.
the PR should be ready for review. please help running the pipeline again
|
/azp run |
|
Commenter does not have sufficient privileges for PR 13512 in repo microsoft/WSL |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@benhillis Merging is blocked and it seems your re-review is needed. Would you mind taking a look again? |
|
Thank you for your contribution! |
Summary of the Pull Request
PR Checklist
Detailed Description of the Pull Request / Additional comments
(closes #13075)
The WSL
--set-sparsecommand requires a boolean value (trueorfalse). The current "MessageSparseVhdDisabled" prompt omitstrue, which causes confusing error messages and prevented sparse VHD from being enabled.This change ensures the command is complete in the "MessageSparseVhdDisabled" prompt:
Validation Steps Performed
Ran
.\bin\x64\Debug\test.bat /name:SimpleTests::SimpleTests::CheckSparseand observed the test case passed: