-
Notifications
You must be signed in to change notification settings - Fork 473
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.
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
PssaCmdletAnalysisEngine fails with "Errors found while formatting file" and no additional data #4942
Comments
@andyleejordan there was a new PSScriptAnalyzer release, there may be a regression with that. @cythrault do you have the newer psscriptanalyzer installed separate from the extension? |
@JustinGrote Negative: And the only PSScriptAnalyzer module folder I see on that system is v1.21.0 which is under $env:USERPROFILE\.vscode\extensions\ms-vscode.powershell-2024.0.0\modules\PSScriptAnalyzer |
@cythrault if you run Invoke-Scriptanalyzer on your script separately does it work fine? As you said it's a 4k+ line module so you may be running into an edge case with ScriptAnalyzer. VSCode is mostly a passthrough to that functionality so the issue would most likely be fixed there if anywhere instead of this repo. I cannot reproduce without a copy of your module, I'm not seeing any issues ATM. |
This issue has been labeled as needing feedback and has not had any activity a week. It has been closed for housekeeping purposes. |
Prerequisites
Summary
Document formatting fails on seemingly random pieces of code. Even if diagnostics enabled, there no meaningful errors aside from the extension logging these:
PowerShell Version
Visual Studio Code Version
Extension Version
Steps to Reproduce
The psm1 file failing to be formatted contains >4000 lines of code which execute without a problem. However, I'm unable to locate the appropriate code that might trigger this issue.
Visuals
No response
Logs
u
The text was updated successfully, but these errors were encountered: