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

Ouverte

#7,806 ouverte le 20/5/2026 3 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté: 3/5
Temps estimé: 1-2 jours
Accessibilité débutants: 55/100

Type d'issue: Bug
Clarté: Plutôt claire
Activité: Calme
Stack technique: git, typescript
Domaine: build-system, developer-experience

Piste de recherche

Commencez par comparer la configuration d’installation ou des dépendances de 4.100.3 et 4.117.0, en vérifiant notamment si @vscode/fs-copyfile est inclus pour l’extension intégrée vscode.git. Reproduisez l’erreur de module manquant, puis vérifiez qu’une installation propre active Source Control sans installer manuellement le package.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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