forcedotcom / forcedotcom/code-analyzer
[Feedback] InternalExecutionErrors in sfca v5.12
- Lingua principale
- TypeScript
- Stelle
- 240
- Fork
- 52
- Merge medio
- 1g 23h
- PR unite (30g)
- 5
Descrizione
### 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 --config-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.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- cli, devtools
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100