Skip to content

UseCorrectCasing: Do not use CommandInfoCache when CommandInfoParameters property throws due to runspace affinity problem of PowerShell engine - #1523

Merged
Christoph Bergmeister (bergmeister) merged 3 commits into
PowerShell:masterfrom
bergmeister:UseCorrectCasing-DoNotUseCache
Jun 30, 2020
Merged

UseCorrectCasing: Do not use CommandInfoCache when CommandInfoParameters property throws due to runspace affinity problem of PowerShell engine#1523
Christoph Bergmeister (bergmeister) merged 3 commits into
PowerShell:masterfrom
bergmeister:UseCorrectCasing-DoNotUseCache

Conversation

@bergmeister

@bergmeister Christoph Bergmeister (bergmeister) commented Jun 13, 2020

Copy link
Copy Markdown
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

@bergmeister
Christoph Bergmeister (bergmeister) marked this pull request as ready for review June 13, 2020 19:46
@bergmeister Christoph Bergmeister (bergmeister) changed the title 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 Jun 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Collection was modified; enumeration operation may not execute when running Invoke-ScriptAnalyzer

2 participants