forcedotcom / forcedotcom/code-analyzer

[Feedback] InternalExecutionErrors in sfca v5.12

Offen
#2,069 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
TypeScript
Sterne
240
Forks
52
Ø Merge
1 T. 23 Std.
Gemergte PRs (30 T.)
5

Beschreibung

### 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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
java
Bereich
cli, devtools
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Ruhig
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.