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.

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

[BUG] Analysis failed: spawn ENAMETOOLONG #18

Open
marcopinder opened this issue Sep 27, 2023 · 3 comments
Open

[BUG] Analysis failed: spawn ENAMETOOLONG #18

marcopinder opened this issue Sep 27, 2023 · 3 comments
Labels
BUG P3 Rarely Malfunction

Comments

@marcopinder
Copy link

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
image

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

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

@jfeingold35 jfeingold35 added the BUG P3 Rarely Malfunction label Sep 27, 2023
@git2gus
Copy link

git2gus bot commented Sep 27, 2023

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

@naveenkn456
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG P3 Rarely Malfunction
Projects
None yet
Development

No branches or pull requests

3 participants