coder / coder/code-server

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

Aberta
#7,806 3 comentários 0 reações 0 responsáveis Ver no GitHub
bug code-server
Linguagem predominante
TypeScript
Estrelas
79.3k
Forks
6.8k
Merge médio
2d 6h
PRs com merge (30d)
41

Descrição

### Is there an existing issue for this?

- [x] 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

```shell

```

### 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

_No response_

Guia de contribuição

Abrir o guia de contribuição

Direção de pesquisa

Comece comparando a configuração de instalação ou de dependências de 4.100.3 e 4.117.0, com foco em verificar se @vscode/fs-copyfile está incluído para a extensão integrada vscode.git. Reproduza o erro de módulo ausente e, em seguida, verifique se uma instalação limpa ativa o Source Control sem instalar o pacote manualmente.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Stack de tecnologia
git, typescript
Domínio
build-system, developer-experience
Tipo de issue
Bug
Dificuldade
3/5
Tempo estimado
1-2 dias
Status de atividade
Pouca atividade
Clareza
Razoavelmente clara
Facilidade para iniciantes
55/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.