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.

Sign up for GitHub

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

Jump to bottom

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

Merged
merged 3 commits into from
Jun 30, 2020
Merged

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

merged 3 commits into from
Jun 30, 2020

Conversation

bergmeister
Copy link
Collaborator

@bergmeister bergmeister commented Jun 13, 2020 •
edited
Loading

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 bergmeister mentioned this pull request Jun 13, 2020
Closed
@bergmeister bergmeister marked this pull request as ready for review June 13, 2020 19:46
@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
@bergmeister bergmeister merged commit d04c039 into PowerShell:master Jun 30, 2020
@bergmeister bergmeister mentioned this pull request Jul 2, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@rjmholt rjmholt rjmholt approved these changes

@JamesWTruher JamesWTruher Awaiting requested review from JamesWTruher

Assignees
No one assigned
Labels
Issue - Bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Collection was modified; enumeration operation may not execute when running Invoke-ScriptAnalyzer
2 participants
@bergmeister @rjmholt