fix(scoop-info): Fix error message when manifest is not found #4935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes #4928.
Abort message no longer references the last bucket searched via
Find-Manifest
Motivation and Context
Fixes #4928
How Has This Been Tested?
This is an edge case abort message, and there appear to be no tests that use the string literal
Could not find manifest
which suggests the text is never explicitly matched against during test execution.My assumption here is that the tests should pass, sadly I don't actually have a powershell build environment, and I wouldn't really know how to start building one to include
BuildHelpers
and other PS modules referenced in test/bin/test.ps1Checklist:
develop
branch.I have updated the documentation accordingly.Documentation change not required.