Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File watchers in WSL do not work at all #4517

Closed
justinmchase opened this issue Feb 21, 2021 · 3 comments
Closed

File watchers in WSL do not work at all #4517

justinmchase opened this issue Feb 21, 2021 · 3 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@justinmchase
Copy link

Issue Type: Bug

Running dotnet watch test runs once and never detects a file change. Similarly VSCode appears to be affected by this issue where the C# errors dont go away until after a rebuild and I have to reload the window anytime I add / remove a file. VSCode intellisense for C# is constantly failing and requiring a reload of the window to work again, very surprisingly bad experience for C# of all things.

VS Code version: Code 1.53.2 (622cb03f7e070a9670c94bae1a45d78d7181fbd4, 2021-02-11T11:48:04.245Z)
OS version: Windows_NT x64 10.0.19041
Remote OS version: Linux x64 4.19.104-microsoft-standard

System Info
Item Value
CPUs Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz (4 x 3399)
GPU Status 2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 15.93GB (7.53GB free)
Process Argv --crash-reporter-id 97723867-d03c-4ab3-baa8-5b03e75c8e01
Screen Reader no
VM 0%
Item Value
Remote WSL: Ubuntu
OS Linux x64 4.19.104-microsoft-standard
CPUs Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz (4 x 3399)
Memory (System) 12.43GB (10.56GB free)
VM 0%
Extensions (16)
Extension Author (truncated) Version
bracket-pair-colorizer Coe 1.0.61
remote-wsl ms- 0.53.4
debugger-for-chrome msj 4.12.12
vscode-apollo apo 1.18.2
insert-unicode bru 0.10.0
better-toml bun 0.3.2
vscode-eslint dba 2.1.14
EditorConfig Edi 0.16.4
prettify-json moh 0.0.3
vscode-azurefunctions ms- 1.2.1
csharp ms- 1.23.9
azure-account ms- 0.9.6
rust rus 0.7.8
crates ser 0.5.6
rust-pack Swe 0.2.29
capitalize via 0.1.0
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30256636
pythonvsdeb440:30248342
pythonvsded773:30248341
pythonvspyt875:30259475
pythontb:30258531

@aeschli
Copy link
Contributor

aeschli commented Feb 22, 2021

Likely #3959.
Can you confirm that this is with files on /mnt/c ?

We now have a fix for that in the upcoming stable (or latest insiders): #4455

@aeschli aeschli transferred this issue from microsoft/vscode Feb 22, 2021
@bamurtaugh bamurtaugh added the info-needed Issue requires more information from poster label Feb 25, 2021
@justinmchase
Copy link
Author

It is actually in /mnt/d for me but yeah probably the same issue. I am changing the files from within linux in this case and there are no events in the remote.

@aeschli
Copy link
Contributor

aeschli commented Feb 26, 2021

duplicate of #3959. Switching to the Linux FS is also much better for performance.

@aeschli aeschli closed this as completed Feb 26, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants