UseCorrectCasing: Do not use CommandInfoCache when CommandInfoParameters property throws due to runspace affinity problem of PowerShell engine by bergmeister · Pull Request #1523 · PowerShell/PSScriptAnalyzer
PowerShell / PSScriptAnalyzer Public
-
Notifications
You must be signed in to change notification settings - Fork 409
Merged
merged 3 commits into
Conversation
Collaborator
PR Summary
Fixes #1516 by not using the cache if the sporadic PowerShell bug happens due to the runspace affinity PowerShell/PowerShell#4003
PR Checklist
- PR has a meaningful title
- Use the present tense and imperative mood when describing your changes
- Summarized changes
- Change is not breaking
- Make sure all
.cs,.ps1and.psm1files have the correct copyright header - Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
- This PR is ready to merge and is not Work in Progress.
- If the PR is work in progress, please add the prefix
WIP:to the beginning of the title and remove the prefix when the PR is ready.
- If the PR is work in progress, please add the prefix
…erty has runspace affinity problems
UseCorrectCasing: Do not use CommandInfoCache because Parameters property has runspace affinity problems
UseCorrectCasing: Do not use CommandInfoCache when CommandInfoParameters property throws due to runspace affinity problem of PowerShell engine
rjmholt
approved these changes
d04c039
into
PowerShell:master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
