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] Exception in retirejs engine of latest beta scanner #1469

Closed
rtoepfer opened this issue May 17, 2024 · 3 comments
Closed

[BUG] Exception in retirejs engine of latest beta scanner #1469

rtoepfer opened this issue May 17, 2024 · 3 comments

Comments

@rtoepfer
Copy link

Running Security Scan
› Warning: Plugin @salesforce/sfdx-scanner (4.1.0) differs from the version
› specified by sf (3.24.0)
Warning: We're continually improving Salesforce Code Analyzer. Tell us what you think! Give feedback at https://research.net/r/SalesforceCA
/home/vsts/.local/share/sf/node_modules/@salesforce/sfdx-scanner/lib/lib/retire-js/RetireJsEngine.js:248
throw new core_1.SfError(message);
^

SfError: Cannot read properties of undefined (reading 'map')
at RetireJsEngine.processOutput (/home/vsts/.local/share/sf/node_modules/@salesforce/sfdx-scanner/lib/lib/retire-js/RetireJsEngine.js:248:19)
at ChildProcess. (/home/vsts/.local/share/sf/node_modules/@salesforce/sfdx-scanner/lib/lib/retire-js/RetireJsEngine.js:171:30)
at ChildProcess.emit (node:events:519:28)
at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
cause: undefined,
actions: undefined,
exitCode: 1
}

scanner run Issue Template

Fill out this template to submit your Code Analyzer issue.

Description:

Documentation:

Steps To Reproduce:

Expected Behavior:

Screenshots:

Desktop:

Additional Context:

Workaround:

Urgency:

@johnbelosf
Copy link
Collaborator

@rtoepfer can you please fill in the above template? Otherwise unfortunately we'll need to close this issue

@stephen-carter-at-sf
Copy link
Collaborator

stephen-carter-at-sf commented May 17, 2024

What is the output
sf --version
on your machine?

Also, can you try to run
sf scanner run -e retire-js -t
on each file or folder you have and narrow down what file it might be complaining about. My hunch is that our convertStringToResulveObj may be hiccupping on a result for some reason. If you can find just a file and can consistently reproduce... can you share with us the file that it is complaining about?

@stephen-carter-at-sf
Copy link
Collaborator

Closing issue since no response has been provided and the template was not filled out.

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

No branches or pull requests

3 participants