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

Abierto

#7,806 abierto el 20/5/2026 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad: 3/5
Tiempo estimado: 1-2 días
Aptitud para principiantes: 55/100

Tipo de issue: Error
Claridad: Bastante claro
Estado de actividad: Tranquilo
Stack tecnológico: git, typescript
Área: build-system, developer-experience

Línea de trabajo

Comienza comparando la configuración de instalación o de dependencias de 4.100.3 y 4.117.0, centrándote en si @vscode/fs-copyfile está incluido para la extensión integrada vscode.git. Reproduce el error de módulo faltante y, después, verifica que una instalación limpia active Source Control sin instalar manualmente el paquete.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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