[BUG] Analysis failed: spawn ENAMETOOLONG

[marcopinder]

Describe the bug
Analysis failed with a 'spawn ENAMETOOLONG' error.

To Reproduce
When right-clicking on the 'classes' folder, or selecting all class files and right-clicking, I choose 'SFDX: Scan selected files of folders with Code Analyzer'. However, this generates an error 'Analysis failed: spawn ENAMETOOLONG'.

Expected behavior
For the scan to complete successfully and print any violations identified.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10 Enterprise
• Browser: Chrome
• Version: 116.0.5845.188 (Official Build) (64-bit)
• VS Code Version: 1.81.1
• Salesforce Code Analyzer VS Code Extension Version: 0.1.1

"Workaround": No workaround to do this in VS Code.

"Urgency": Not business-stopping, but renders the functionality almost pointless as I don't want to do this on a class by class basis.

[jfeingold35]

@marcopinder , thanks for bringing this to our attention. We'll add it to our backlog.

[git2gus]

This issue has been linked to a new work item: W-14195123

[naveenkn456]

Is this issue fixed? Today I tried the extension in the VS code and faced the same error.

[martykopka]

This is still a problem. Is there any news on when this will be resolved, when a work around or a fix will be provided. We have a project with hundreds of classes and so we hit this issue as it tries to run on a folder and the resulting expanded line is too long. Checking 100's of files one by one is simply not feasible and makes this tool unusable in automated situations.