Anders Schack-Mulligen

This looked like a minor perf improvement, which I randomly came across. Let's see what dca thinks.

Java: Add support for data flow through thrown exceptions.

4

This adds support for exception flow. A test is included that shows some of what works and what doesn't. Currently we get spurious flow due to imprecisions in type pruning....

If one source could flow to another with a different tracked type, we would end up duplicating the reported results for the latter source.

The extension buffers progress messages from the CLI instead of showing them as they happen

2

**Describe the bug** When the extension runs CodeQL CLI commands and those commands attempt to report progress through stderr then the messages are buffered and only shown after the CLI...

Handle large (>4GB) SARIF results files on reopen

8

**Describe the bug** Support for large sarif files was added in https://github.com/github/vscode-codeql/pull/1004 which "fixed" https://github.com/github/vscode-codeql/issues/735. However, this only works one time. When the sarif file already exists and the results...

QL debug in VSCode: switching dbs has no effect.

7

**Describe the bug** If I enter debug mode for a query in order to be able to quick-eval inside a shared qlpack and I then select a different db then...

This makes two changes to the fieldFlowBranchLimit interpretation: * The count is adjusted to properly count virtual dispatch instead of nodes. This will block less flow and hence result in...