You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Cannot search the code from VSCode Search tab (Crtl+Shift+F) #4172
Describe the bug
I cannot search the code from the VSCode Search tab (Crtl+Shift+F), when the CodeQL database is mounted in the current workspace through "Add Database Source to Workspace".
Right click on the selected database and click on "Add Database Source to Workspace"
Bonus bug: Re-select the database because VSCode switched the context to a workspace
Observe in the "Explorer" tab that the database source is well mounted has "[db source archive]" in your newly created workspace
Right click on this mounted folder and click on "Find in Folder..." (or press Crtl+Shift+F)
Try to search any piece or code that is supposed to be in the database source
Expected behavior
After trying to search some code in the source, we are supposed to get the same results as if the source were mounted has normal folder, rather then a CodeQL database archive.
Hi, thank you for the issue and the detailed steps!
Unfortunately, this is the expected behaviour: the [db source archive] is added as a "virtual" file system, just so that we can link to CodeQL alerts in the source. It doesn't have the same features as a "real" file system (e.g. no editing or searching).
We acknowledge that this isn't ideal, but changing the behaviour is not something we're currently able to prioritise. I'm closing this issue now, but don't hesitate to reach out if you have any other issues in future!
Activity
shati-patel commentedon Oct 23, 2025
Hi, thank you for the issue and the detailed steps!
Unfortunately, this is the expected behaviour: the
[db source archive]is added as a "virtual" file system, just so that we can link to CodeQL alerts in the source. It doesn't have the same features as a "real" file system (e.g. no editing or searching).We acknowledge that this isn't ideal, but changing the behaviour is not something we're currently able to prioritise. I'm closing this issue now, but don't hesitate to reach out if you have any other issues in future!