Vscode: files.watcherExclude not working on latest version!

[GregLarden]

NOT multi-root

VS Code :
Version: 1.29.1 (user setup)
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:13:36.375Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64

Steps to Reproduce:
This is my configuration in
User Settings:
"files.useExperimentalFileWatcher": false,
"files.watcherExclude": {
"/src/assets/": true,
"/node_modules/*/": true
},

Workspace Settings;
"files.watcherExclude": {
"/src/assets/": true,
"/node_modules/*/": true
},

Does this issue occur when all extensions are disabled?: Yes

[vscodebot[bot]]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• files.watcherExclude setting is not working in multi-root workspace (#40898)
  

[Tyriar]

I don't think that's a valid path. Here's the form used in the default value, I suggest copying that:

  "files.watcherExclude": {
    "**/.git/objects/**": true,
    "**/.git/subtree-cache/**": true,
    "**/node_modules/*/**": true
  }

[GregLarden]

@Tyriar , I have tried "**/assets/**": true, AND **/assets/customstyles/**": true

None of the suggestions I found online or paths I have tried worked.

Any tips on how to get the file watcher to ignore changes in all sub folders/files under the assets folder?

[Tyriar]

I can repro using both files.useExperimentalFileWatcher being true or false and this setting:

  "files.watcherExclude": {
    "**/.git/objects/**": true,
    "**/.git/subtree-cache/**": true,
    "**/node_modules/*/**": true
  }

Changing ./node_modules/somefolder/somefile fires an event.

@bpasero any ideas what could have caused? I haven't touched the file watcher since April

[Tyriar]

This is probably https://github.com/Microsoft/vscode/issues/4089

[bpasero]

@Tyriar I can reproduce and I am puzzled too, will have a look.

[bpasero]

@Tyriar looks like a red herring to me, I tried on Windows with NSFW and correctly get the ignored message:

The same is true for the C# watcher. Though the output is misleading, I can see that a NORMALIZED event is reported, however it is being ignored in our system (thats what the other message shows):

[GregLarden]

Curious why this is closed without a solution?