[Feedback] InternalExecutionErrors in sfca v5.12
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start with issue #1497 and the provided sf code-analyzer command and SFGE settings. Determine what the 300000 ms path-evaluation timeout means for a .cls scan and whether the reported InternalExecutionError indicates incomplete analysis; done means documenting or correcting that behavior with a clear explanation of timeout handling.
Written by the indexing model from the issue text.
Description
Feedback
Hi,
We are using SFCA v5.12 and we are still seeing InternalExecutionError coming in the logs for our SFGE scan. This is our SFGE settings:
sfge:
java_thread_count: 10
java_thread_timeout: 300000
The command we use is: sf code-analyzer run --rule-selector sfge --target <sfge_target_file> --config-file --output-file <output_file>
I can see from this ticket (https://github.com/forcedotcom/code-analyzer/issues/1497) there have been improvements made from v5.11 onwards but we do still see errors such as 'Path evaluation timed out after 300000 ms' , does this mean the scanner is unable to scan through the enter .cls file? Because if we don't set a timeout the scan doesn't seem to end. Please help to advise, thanks
Context
No response
Suggestions
No response
Additional Information
No response
Are you interested in contributing to this project?
Yes, I'd like to contribute.
- Dominant language
- TypeScript
- Stars
- 240
- Forks
- 52
- Avg merge
- 9h 48m
- Merged PRs (30d)
- 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from forcedotcom/code-analyzer
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
forcedotcom/code-analyzer#2094 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
forcedotcom/code-analyzer#2093 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
forcedotcom/code-analyzer#2091 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
forcedotcom/code-analyzer#2090 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
forcedotcom/code-analyzer#2099 ·
All issues in forcedotcom/code-analyzer
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·