Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Quick-eval results cannot be compared

Open
#873 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
developer-experience, frontend

Research direction

Start from the Query History view's Compare Results command and the comparison view used for Quick Evaluation runs. Reproduce both same-predicate and different-predicate cases, then trace how predicate names and result schemas reach the table-name dropdown. Done means matching predicates compare correctly, compatible differing schemas use a placeholder, and incompatible schemas show an empty comparison with a suitable warning.

Written by the indexing model from the issue text.

Description

bug VSCode

Describe the bug

When running the Compare Results command from the Query History view on the results of Quick Evaluation queries, the comparison view is empty, with no table names in the dropdown. If two different predicates were run, this also throws an error Schema undefined not found..

Version
CodeQL extension version: 1.4.8
CodeQL CLI version: 2.5.5

To reproduce

  • Create a query file with two predicates. 
    int i1() { result = 1 }
int i2() { result = 2 }
select 1
  • Quick-evaluate i1 twice. Select the two runs in Query History, right click, Compare Results.
    • This produces an empty compare view with no table names in the dropdown.
  • Quick-evaluate i1 then i2. Select the two runs in Query History, right click, Compare Results.
    • This fails with an error Schema undefined not found.
    • It also produces the same empty compare view with no table names in the dropdown.

Expected behavior

  • When the predicate name and columns match, show the quick-eval predicate name in the dropdown, and show a comparison of results.
  • If the predicate names do not match, but the two schemas are compatible, attempt to compare the results, with a placeholder table name in the dropdown.
  • If the schemas aren't compatible, show an empty comparison with a suitable warning message.
Dominant language
TypeScript
Stars
539
Forks
240
Avg merge
2d 6h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/vscode-codeql

All issues in github/vscode-codeql

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.