microsoft / microsoft/vscode-remote-release
Files on /mnt/ do not refresh when is modified from external source
Open
@aeschli is already working on this.
Since May 4, 2021.
bug
wsl
- Dominant language
- Dockerfile
- Stars
- 4.2k
- Forks
- 470
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 1
Description
Issue Type: Bug
For example, when working with WSL, if file resides on the host (/mnt/**) then from the distro console you modify the files while vscode has that file open (on current view), the vscode view doesnt refresh unless you force a screen change (swaping view on files or maximizing/minimizing vscode)
VS Code version: Code 1.55.2 (3c4e3df9e89829dce27b7b5c24508306b151f30d, 2021-04-13T09:35:57.887Z)
OS version: Windows_NT x64 10.0.19041
Remote OS version: Linux x64 4.19.128-microsoft-standard
System Info
| Item | Value |
|---|---|
| CPUs | AMD Ryzen 7 1700 Eight-Core Processor (16 x 3600) |
| 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.94GB (4.47GB free) |
| Process Argv | --crash-reporter-id a48508eb-035b-43c4-b920-cba7ac91df90 |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: Debian |
| OS | Linux x64 4.19.128-microsoft-standard |
| CPUs | AMD Ryzen 7 1700 Eight-Core Processor (16 x 3600) |
| Memory (System) | 12.43GB (10.37GB free) |
| VM | 0% |
Extensions (13)
| Extension | Author (truncated) | Version |
|---|---|---|
| remote-wsl | ms- | 0.54.6 |
| slim | sia | 0.1.2 |
| vscode-ruby | win | 0.28.0 |
| rails | bun | 0.17.0 |
| vscode-gemfile | bun | 0.4.0 |
| solargraph | cas | 0.21.1 |
| githistory | don | 0.6.16 |
| gitlens | eam | 11.4.1 |
| code-runner | for | 0.11.3 |
| ruby-rubocop | mis | 0.8.5 |
| ruby | reb | 0.28.1 |
| slim | sia | 0.1.2 |
| vscode-ruby | win | 0.28.0 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.