-
Notifications
You must be signed in to change notification settings - Fork 50
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] Graph scan throws Internal Exception in output and log when scanning a method that contains Describe Tabs
code
#1191
Comments
This issue has been linked to a new work item: W-14169354 |
Is there any workaround to this? Or is there a way we can suppress scanning for this method? Since no Error code being generated for this, I don't know how to suppress scanning of this - our scanner logs are bombarded with this and almost all other classes (after running for hours) are reporting either timeout or Internal Server Error like this:
|
@vc4u , I understand your frustration, but unfortunately I don't think there's a workaround for this. We've added it to our backlog, and we can assess the level of effort that would be involved in a fix. We appreciate your patience in the meantime. |
Describe Tabs
codeDescribe Tabs
code
Marking this as a duplicate of #1497 |
Describe the bug
DFA scan generated output report and log files are showing an internal exception.
Error:
Method:
To Reproduce
Execute following command for the method provided above:
sf scanner run dfa -f html -o CodeAnalyzerDFA.html -p ./force-app/main/default -t ./force-app/main/default/classes/util.cls#getIconName --category "Security" --rule-thread-count 10 --sfgejvmargs "-Xmx4g" --pathexplimit "-1" --rule-thread-timeout 90000
Expected behavior
Error should not be thrown, there is NO FLS or CRUD violation in provided method.
Desktop (please complete the following information):
"Workaround":
No
"Urgency":
"Business stopping" as unable to scan project due to multiple errors thrown on similar lines all over the code base.
The text was updated successfully, but these errors were encountered: