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

QL debug in VSCode: switching dbs has no effect.

Open
#2,654 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode

Research direction

Reproduce the issue with the CodeQL: Debug Query and CodeQL: Debug Selection commands while switching databases in VS Code. Trace the database-selection state used by the debug query flow; done means a debug selection always queries the currently selected database, including after switching from the initial database.

Written by the indexing model from the issue text.

Description

bug VSCode

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 querying still happens on the prior db

Version
CodeQL extension version: 1.8.8
CodeQL CLI version: 2.14.0
Platform: darwin x64

To reproduce

  1. Go to a .ql file
  2. Right-click -> "CodeQL: Debug Query"
  3. Switch to a different database
  4. Right-click -> "CodeQL: Debug Selection" on any predicate

Expected behavior
I'd expect querying to always happen on the currently selected database.

Additional context

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.