Source Control is stuck in 'scanning folder for git repository', fix found

オープン

#7,806 2026年5月20日に作成コメント 3 件リアクション 0 件担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度: 3/5
見積もり時間: 1〜2日
初心者へのやさしさ: 55/100

issue の種類: バグ
明瞭さ: おおむね明確
活発さ: 静か
技術スタック: git, typescript
領域: build-system, developer-experience

調査の方向性

まず 4.100.3 と 4.117.0 のインストールまたは依存関係の設定を比較し、組み込みの vscode.git 拡張機能に @vscode/fs-copyfile が含まれているかどうかを確認します。不足しているモジュールのエラーを再現し、その後、パッケージを手動でインストールしなくても、クリーンインストールで Source Control が有効になることを確認します。

索引モデルが issue の本文から書いたものです。

説明

bug code-server

Is there an existing issue for this?

I have searched the existing issues

OS/Web Information

Web Browser: Chrome
Local OS: Macos
Remote OS: Debian 12
Remote Architecture: x86
code-server --version: 4.117.0 and more

Steps to Reproduce

I have been using version 4.100.3 all along, and today I tried to update to version 4.117.0 (npm install) code-server@4.117.0 --unsafe-perm ）， After the update, it was found that the Source Control has been stuck in "scanning folder for git repository".

Expected

Source Control should show something

Actual

I searched for @ builtin git in the extension and found that the git extension is not active.

I found the relevant logs in the 'Issues' window:

2026-05-21 01:11:21.601 [error] Activating extension vscode.git failed due to an error:
2026-05-21 01:11:21.601 [error] Error: Cannot find module '@vscode/fs-copyfile'

I also tried switching between 4.116.0 and 4.117.0.
I am trying to install npm install @vscode/fs-copyfile and reload window, and in the end it was fixed.

So was @vscode/fs-copyfile lost in the default installation?

Logs

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

Yes, this is also broken in native VS Code

Does this bug reproduce in VS Code web?

Yes, this is also broken in VS Code web

Does this bug reproduce in GitHub Codespaces?

Yes, this is also broken in GitHub Codespaces

Are you accessing code-server over a secure context?

I am using a secure context.

Notes