JS/TS Analyse 2.20.4 Runs Extremely Slow
- Vorherrschende Sprache
- CodeQL
- Sterne
- 10.1k
- Forks
- 2.1k
- Ø Merge
- 2 T. 15 Std.
- Gemergte PRs (30 T.)
- 141
Beschreibung
Pipelines had been taking >90m to run the CodeQL `github/codeql-action/analyze@v3` step sicne 2.20.4. When reverting back to 2.20.3 via
```yaml
...
- name: "Initialize CodeQL"
uses: github/codeql-action/init@v3
with:
tools: https://github.com/github/codeql-action/releases/download/codeql-bundle-v2.20.3/codeql-bundle-linux64.tar.zst
languages: javascript-typescript
...
```
the issue is resolved. It is difficult to see why this is happening, but in our case the codebase is large (`CodeQL scanned 8401 out of 8401 TypeScript files and 1568 out of 1569 JavaScript files in this invocation.`). Normal runtime for this job is about 10 minutes with 32 GB memory and 40 (32 effective) CPUs
Let me know if I can help resolve the issue by providing additional details about the codebase. I suspect something in particular about this codebase may be running inefficiently, as no other JS/TS scans within the enterprise have been impacted so far
Beitragsleitfaden
Rechercherichtung
Start with the workflow's CodeQL init and analyze steps, reproducing the JavaScript/TypeScript scan with bundle 2.20.4 and comparing it with 2.20.3. Investigate the analysis performance for the reported 8,401 TypeScript and 1,569 JavaScript files; done means identifying the cause of the regression and returning runtime toward the usual 10 minutes.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- javascript, typescript
- Bereich
- performance, security
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100