Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Distribution is invalid after an upgrade

未關閉
#851 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
typescript, vscode
領域
tooling

研究方向

報告沒有指出實作檔案或測試。首先追蹤 workspace 狀態在升級期間如何選取及刪除 CodeQL 發行版,然後重現所描述的雙 workspace 操作序列。完成的標準是,未升級的 workspace 不再解析已刪除的發行版,且 CodeQL 命令可以執行。

由索引模型根據 Issue 內容生成。

描述

bug VSCode

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:

  1. Open two workspaces and ensure the installed version of the cli is outdated
  2. Upgrade the cli versin in one of the workspaces
  3. Do not upgrade in the other workspace
  4. 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.
  5. Now, doing anything codeql related in the non-upgraded workspace will cause the error.
主要語言
TypeScript
星號
539
分支
240
平均合併
2 天 18 小時
30 天內合併 PR
37

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

github/vscode-codeql 的其他 Issue

查看 github/vscode-codeql 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。