ESLint warnings/errors do not update

[willresen]

Issue Type: Bug

When loading a file with linting errors, they are initially displayed correctly. However, these errors do not disappear if they are fixed nor are new errors displayed until the file is closed and reopened.

Extension version: 1.0.1891 VS Code version: Code 1.43.2 (0ba0ca52957102ca3527cf479571617f0de6ed50, 2020-03-24T07:38:38.248Z) OS version: Windows_NT x64 10.0.18363

System Info

Item	Value
CPUs	AMD Ryzen 7 2700X Eight-Core Processor (16 x 3700)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: unavailable_off rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	31.95GB (18.98GB free)
Process Argv	C:\Users\Will Resen\Downloads\Table 1-Grid view.csv
Screen Reader	no
VM	0%

[dlebu]

Thanks for reaching out. This seems like a bug in our language services. Adding @daytonellwanger to take a closer look.

[DaNubCoding]

I'm encountering the same issue, please fix it thanks, it is a big problem with live share and is hindering a lot of debugging processes while live sharing.

[derekbekoe]

We’re not able to prioritize this issue over the other higher-impact issues we receive every week, based on the votes and comments from others in the community and our understanding of the issue. We understand this may be disappointing; we've all been there, whether in this project or others we've contributed to. However, rest assured that we love your input. If you feel it deserves to stay open, then clarify your use case and contact us to let us know how severe it’s for you.