Distribution is invalid after an upgrade
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript, vscode
- Domain
- tooling
Research direction
The report does not name an implementation file or test. Start by tracing how workspace state selects and deletes CodeQL distributions during an upgrade, then reproduce the two-workspace sequence described. Done means the non-upgraded workspace no longer resolves a deleted distribution and CodeQL commands run.
Written by the indexing model from the issue text.
Description
Describe the bug
A bug was reported where a user upgraded and then was no longer able to run any codeql commands. On deeper inspection, we noticed that the path to the distribution was incorrect. The user was getting errors like:
Caused by: java.nio.file.NoSuchFileException: /Users/.../Library/Application Support/Code/User/globalStorage/github.vscode-codeql/distribution9/codeql/tools/codeql.jar
The actual distribution was located at .../distribution10/..., not .../distribution9/....
To reproduce
I haven't tried to reproduce, but suspect that the problem is the following:
- Open two workspaces and ensure the installed version of the cli is outdated
- Upgrade the cli versin in one of the workspaces
- Do not upgrade in the other workspace
- I think the non-upgraded workspace will still point to the old distribution even though it has been deleted.
- It might be that you need to ensure the non-upgraded workspace has already initialized its codeql instance.
- Now, doing anything codeql related in the non-upgraded workspace will cause the error.
- Dominant language
- TypeScript
- Stars
- 539
- Forks
- 240
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 29
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/vscode-codeql
-
bug VSCode
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/vscode-codeql#4471 · 1 comment ·
-
bug enhancement VSCode
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/vscode-codeql#592 · 2 comments ·
-
enhancement VSCode
Difficulty 3/5 1-2 days Newbie friendliness 55/100
github/vscode-codeql#4432 · 1 comment ·
-
bug VSCode
Difficulty 3/5 1-2 days Newbie friendliness 52/100
github/vscode-codeql#4356 ·
-
bug VSCode
Difficulty 3/5 1-2 days Newbie friendliness 64/100
github/vscode-codeql#4339 · 1 comment ·
All issues in github/vscode-codeql
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·