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] InternalExecutionError - Graph Engine identified your source and sink #1667

Closed
aleksaQuadrix opened this issue Nov 4, 2024 · 1 comment

Comments

@aleksaQuadrix
Copy link

Have you tried to resolve this issue yourself first?

Yes

Bug Description

I've ran the analyzer to prepare my code for AppExchange Security Review, however, I've been getting this:
"2","3","C:\Projects[]\sync_streamer\force-app\main\default\classes\SyncSettingsController.cls","42","37","SyncSettingsController","getMetadataSettingsOptions","","","","InternalExecutionError","Graph Engine identified your source and sink, but you must manually verify that you have a sanitizer in this path. Then, add an engine directive to skip the path. Next, create a Github issue for the Code Analyzer team that includes the error and stack trace. After we fix this issue, check the Code Analyzer release notes for more info. Error and stacktrace: UnexpectedException: Did not expect NOT_A_MATCH when ranking parameter match. parameterType = List, type = OrderedTreeSet{internalList=[NULL, Object]}: com.salesforce.graph.ops.TypeableUtil.rankParameterMatch(TypeableUtil.java:211);com.salesforce.graph.vertex.Typeable.rankParameterMatch(Typeable.java:41);com.salesforce.graph.ops.MethodTypeMatchUtil.getMatchRank(MethodTypeMatchUtil.java:191);com.salesforce.graph.ops.MethodTypeMatchUtil.parameterTypesMatch(MethodTypeMatchUtil.java:136);com.salesforce.graph.ops.MethodUtil.getInvoked(MethodUtil.java:358);com.salesforce.graph.ops.MethodUtil.getInvoked(MethodUtil.java:158)","https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/apexflsviolation-rule.html","InternalExecutionError","sfge"

Output / Logs

"2","3","C:\Projects[]\sync_streamer\force-app\main\default\classes\SyncSettingsController.cls","42","37","SyncSettingsController","getMetadataSettingsOptions","","","","InternalExecutionError","Graph Engine identified your source and sink, but you must manually verify that you have a sanitizer in this path. Then, add an engine directive to skip the path. Next, create a Github issue for the Code Analyzer team that includes the error and stack trace. After we fix this issue, check the Code Analyzer release notes for more info. Error and stacktrace: UnexpectedException: Did not expect NOT_A_MATCH when ranking parameter match. parameterType = List, type = OrderedTreeSet{internalList=[NULL, Object]}: com.salesforce.graph.ops.TypeableUtil.rankParameterMatch(TypeableUtil.java:211);com.salesforce.graph.vertex.Typeable.rankParameterMatch(Typeable.java:41);com.salesforce.graph.ops.MethodTypeMatchUtil.getMatchRank(MethodTypeMatchUtil.java:191);com.salesforce.graph.ops.MethodTypeMatchUtil.parameterTypesMatch(MethodTypeMatchUtil.java:136);com.salesforce.graph.ops.MethodUtil.getInvoked(MethodUtil.java:358);com.salesforce.graph.ops.MethodUtil.getInvoked(MethodUtil.java:158)","https://developer.salesforce.com/docs/platform/salesforce-code-analyzer/guide/apexflsviolation-rule.html","InternalExecutionError","sfge"

Steps To Reproduce

I just ran the dfa command to analyze my project code as it was described in the documentation.

Expected Behavior

No issues

Operating System

Windows 7

Salesforce CLI Version

2.51.6

Code Analyzer Plugin (@salesforce/sfdx-scanner) Version

@salesforce/sfdx-scanner (4.7.0)

Java Version

java version "18.0.1.1" 2022-04-22

Additional Context (Screenshots, Files, etc)

No response

Workaround

No response

Urgency

High

@jfeingold35
Copy link
Collaborator

Closing this individual issue, as it is one of the broad categories of issue being tracked with #1497

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

2 participants