github / github/codeql

C++: Total number of baseline files limit

Aberta
#17,743 29 comentários 0 reações 0 responsáveis Ver no GitHub
question
Linguagem predominante
CodeQL
Estrelas
10.1k
Forks
2.1k
Merge médio
2d 15h
PRs com merge (30d)
141

Descrição

Hey friends, I have quite a large C++ database:

```
codeql database print-baseline -- ${CODEQL_DATABASE_DIR}
Counted a baseline of 27711380 lines of code for cpp.
```

Before running scans, I normally run some simple diagnostic queries to make sure the database looks fine. The queries look for things like:
* Files
* `FunctionCall`s
* `IfStmt`s

When I run these queries on this large database, I get this

```
codeql database analyze ${CODEQL_DATABASE_DIR} --format=sarif-latest --output=calls.sarif ${CODEQL_QUERIES}/qlpacks/cpp-queries/diagnostics/FunctionCalls.ql
Running queries.
[1/1 comp 7.8s] Compiled [...]/qlpacks/cpp-queries/diagnostics/FunctionCalls.ql.
Files.ql: [1/1 eval 36s] Results written to cpp-queries/diagnostics/FunctionCalls.bqrs.
Shutting down query evaluator.
Interpreting results.
Will not interpret file coverage baseline information, since the total number of baseline files is 153738, which is greater than the limit of 50000.
```

The exit code is 0 but `calls.sarif` is empty.

When I run queries from the standard C++ pack, I get the same message.

What does this limit mean? Is there any way to increase it? I didn't find anything either in the docs or in this repo unfortunately, may be missing something though. Thanks!

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Reproduce the behavior with `codeql database print-baseline`, `codeql database analyze`, and the C++ diagnostics query `diagnostics/FunctionCalls.ql`. Start by tracing how baseline file counts are interpreted during SARIF result generation and inspect the standard C++ query pack and relevant documentation. Done means the limit's meaning and configuration options are documented or the empty-result behavior is corrected, with a regression test.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
cpp
Domínio
tooling
Tipo de issue
Bug
Dificuldade
4/5
Tempo estimado
3-5 dias
Status de atividade
Estagnada
Clareza
Precisa de esclarecimento
Facilidade para iniciantes
35/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.