settings files.watcherExclude not working?

Aperta

#7,505 aperta il 30/9/2025 4 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà: 4/5
Tempo stimato: 3-5 giorni
Idoneità per principianti: 25/100

Tipo di issue: Bug
Chiarezza: Da chiarire
Stato di attività: Ferma
Stack tecnologico: typescript, vscode
Ambito: devtools

Direzione di ricerca

Riproduci il comportamento su Windows con uno spazio di lavoro remoto RHEL 9 e le impostazioni files.watcherExclude fornite, quindi confronta il risultato con VS Code nativo e GitHub Codespaces come riportato. Traccia il modo in cui code-server passa queste impostazioni al file watcher e verifica se le esclusioni mirate impediscono il montaggio degli endpoint autofs e rclone; il lavoro è completato quando i percorsi esclusi non vengono né percorsi né montati.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug triage

Is there an existing issue for this?

I have searched the existing issues

OS/Web Information

Web Browser: latest Chrome
Local OS: Windows
Remote OS: RHEL 9
Remote Architecture: x86_64
code-server --version: 4.104.2 b0992ddb3e3b398371da6bcfbe21a70b4d66eb8d with Code 1.104.2

Steps to Reproduce

Our main project folder contains subfolders that make use of autofs + rclone. We do not want code-server attempting to traverse the MANY remote endpoints configured. The solution should be to use VS Code settings files.watcherExclude as implemented from https://github.com/microsoft/vscode/issues/150174

I have this setting in both the FOLDER (/files) and Workspace settings, but it appears to be ignored. Or is there another place to best handle this override?

{
    "files.watcherExclude": {
        "**/**": true,
        "**": true,
        "*": true
    }
}

That should effectively disable files watching completely. Optimally, I would like to use targeted filtering instead (which also does not have any effect) of globally excluding:

{
    "files.watcherExclude": {
        "/*files/cifs/**": true,
        "/*files/nfs/**": true,
        "/*files/s3/**": true,
        "/*files/sftp/**": true
    }
}

Expected

When I do df, I should not see any remote filesystems mounted.

Actual

As soon as I open the project workspace, it begins to crawl through all of the folders, which in turn, begins to mount every endpoint to do more crawling -- ugh!!

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