You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you tried to resolve this issue yourself first?
Yes
Bug Description
I ran "sf scanner run dfa" command to scan org using the code analyzer and in the CSV file I got this kind of issue
"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: ArrayLoadExpression{properties={FirstChild=true, BeginLine=32, DefiningType_CaseSafe=duplicatecriteriacontactcontroller,LastChild=true, DefiningType=DuplicateCriteriaContactController,EndLine=32, childIdx=0, BeginColumn=40}}: com.salesforce.graph.symbols.PathScopeVisitor.afterVisit(PathScopeVisitor.java:761);com.salesforce.graph.symbols.DefaultSymbolProviderVertexVisitor.afterVisit(DefaultSymbolProviderVertexVisitor.java:737);
com.salesforce.graph.vertex.ArrayLoadExpressionVertex.afterVisit(ArrayLoadExpressionVertex.java:58);
com.salesforce.graph.ops.expander.ApexPathExpander.performAfterVisit(ApexPathExpander.java:577);
com.salesforce.graph.ops.expander.ApexPathExpander.visit(ApexPathExpander.java:536);com.salesforce.graph.ops.expander.ApexPathExpander.visit(ApexPathExpander.java:523) "
I did not get the exact cause by reading an issue. please let me know how to resolve this issue for the code analyzer.
This error message means that your source code contains code that Salesforce Graph Engine currently doesn't handle, requiring us to enhance the graph engine to support it. We apologize for the inconvenience here.
This issue is a duplicate of #1497 and thus I'm closing this issue in favor of that one.
Have you tried to resolve this issue yourself first?
Yes
Bug Description
I ran "sf scanner run dfa" command to scan org using the code analyzer and in the CSV file I got this kind of issue
"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: ArrayLoadExpression{properties={FirstChild=true, BeginLine=32, DefiningType_CaseSafe=duplicatecriteriacontactcontroller,LastChild=true, DefiningType=DuplicateCriteriaContactController,EndLine=32, childIdx=0, BeginColumn=40}}: com.salesforce.graph.symbols.PathScopeVisitor.afterVisit(PathScopeVisitor.java:761);com.salesforce.graph.symbols.DefaultSymbolProviderVertexVisitor.afterVisit(DefaultSymbolProviderVertexVisitor.java:737);
com.salesforce.graph.vertex.ArrayLoadExpressionVertex.afterVisit(ArrayLoadExpressionVertex.java:58);
com.salesforce.graph.ops.expander.ApexPathExpander.performAfterVisit(ApexPathExpander.java:577);
com.salesforce.graph.ops.expander.ApexPathExpander.visit(ApexPathExpander.java:536);com.salesforce.graph.ops.expander.ApexPathExpander.visit(ApexPathExpander.java:523) "
I did not get the exact cause by reading an issue. please let me know how to resolve this issue for the code analyzer.
Output / Logs
No response
Steps To Reproduce
I am running "sf scanner run dfa" command for my code from this link step. no 4.
https://developer.salesforce.com/docs/atlas.en-us.packagingGuide.meta/packagingGuide/security_review_code_analyzer_scan.htm
Expected Behavior
Provide an error that We can understand after reading
Operating System
Windows 11 Home Single Language
Salesforce CLI Version
v60.15.0
Code Analyzer Plugin (@salesforce/sfdx-scanner) Version
@salesforce/sfdx-scanner (4.2.0)
Java Version
jdk_x64_windows_hotspot_17.0.11_9
Additional Context (Screenshots, Files, etc)
No response
Workaround
No response
Urgency
High
The text was updated successfully, but these errors were encountered: