-
Notifications
You must be signed in to change notification settings - Fork 51
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
Graph Engine reached the path expansion upper limit (1643). The analysis preemptively stopped running on this path to prevent an OutOfMemory error. Rerun Graph Engine and target this entry method with a larger heap space. #1681
Comments
@rbishnoi-conga , could you please confirm which version of Code Analyzer you're using by running |
Hi,
Got following output for the command sf plugins:
[cid:576cbc72-f66a-4f47-8cdc-158fecf3bcdf]
Thanks & regards,
Rahul Bishnoi,
8824082841
Conga, The Revenue Company
Leave a review
|Support|Community
|
LinkedIn
…________________________________
From: Josh Feingold ***@***.***>
Sent: Monday, November 25, 2024 8:45 PM
To: forcedotcom/sfdx-scanner ***@***.***>
Cc: Rahul Bishnoi ***@***.***>; Mention ***@***.***>
Subject: Re: [forcedotcom/sfdx-scanner] Graph Engine reached the path expansion upper limit (1643). The analysis preemptively stopped running on this path to prevent an OutOfMemory error. Rerun Graph Engine and target this entry method with a larger heap space....
@rbishnoi-conga<https://github.com/rbishnoi-conga> , could you please confirm which version of Code Analyzer you're using by running sf plugins and posting the output?
—
Reply to this email directly, view it on GitHub<#1681 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHTIO4VY7TMLORC7OCKBST32CM5IXAVCNFSM6AAAAABSNHOEUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGI4TMNRRGI>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@rbishnoi-conga , is that supposed to be a screenshot? It doesn't display here on the Issues page so I'm not sure what I'm looking at. |
Hi,
Yes, it was a screenshot, typing out the same thing for your reference:
@salesforce/sfdx-scanner 4.7.0
Uninstalled JIT Plugins:
community 3.3.2
custom-metadata 3.3.37
dev 2.5.0
devops-center 1.2.26
env 3.0.33
functions 1.23.0
signups 2.6.1
@salesforce/sfdx-plugin-lwc-test 1.2.1
Thanks & regards,
Rahul Bishnoi,
8824082841
Conga, The Revenue Company
Leave a review
|Support|Community
|
LinkedIn
…________________________________
From: Josh Feingold ***@***.***>
Sent: Tuesday, November 26, 2024 8:32 PM
To: forcedotcom/sfdx-scanner ***@***.***>
Cc: Rahul Bishnoi ***@***.***>; Mention ***@***.***>
Subject: Re: [forcedotcom/sfdx-scanner] Graph Engine reached the path expansion upper limit (1643). The analysis preemptively stopped running on this path to prevent an OutOfMemory error. Rerun Graph Engine and target this entry method with a larger heap space....
@rbishnoi-conga<https://github.com/rbishnoi-conga> , is that supposed to be a screenshot? It doesn't display here on the Issues page so I'm not sure what I'm looking at.
—
Reply to this email directly, view it on GitHub<#1681 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BHTIO4XWW7PKGXRWEMFNERD2CSEPDAVCNFSM6AAAAABSNHOEUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGA2TAMZSGM>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
@rbishnoi-conga , have you tried any of the troubleshooting steps, or failing that, any of the suggested refactors for working around these issues? |
Graph Engine reached the path expansion upper limit (1643). The analysis preemptively stopped running on this path to prevent an OutOfMemory error. Rerun Graph Engine and target this entry method with a larger heap space.
The text was updated successfully, but these errors were encountered: