Vscode-remote-release: Remote WSL: Source Control not showing changed files

[vitormhenrique]

• VSCode Version: 1.34.20
• Local OS Version: Windows 10
• Remote OS Version: Ubuntu 18.04.2 LTS
• Remote Extension: WSL

Steps to Reproduce:

1. Open a project on WSL with source control
2. Make changes to any file
3. _Source control does not identify changes_
4. Restart vscode
5. vscode will now identify changes and will be able to stage / push to source control

Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No

[niallel]

I saw the same thing when I had only 1GB of memory on my server. Also there were 2 node processes running at 40%.

When I increased to 2GB all the problems went away and git started showing the changes.

[vitormhenrique]

I haven’t tried having remote ssh, but with windows subsystem for linux I don’t have control over the size of the VM ram allocation (do I?)

[joaomoreno]

@vitormhenrique Do any extensions work when you're in that state?

[vitormhenrique]

Mostly, I can still pull data from the GitHub, I can't commit of course because vscode thinks there is nothing changed to be able to stage / commit.

If i do a "push" or"sync" it will figure it out that something changed and will allow to stage / commit.

Check the print screen, the comment is a new info, that the local git is aware of, so on the terminal "git diff" shows the correct changes, but vs code does not show anything under changes.

[joaomoreno]

Do file events work at all? If you create a file using the terminal, does it show up in the file explorer?

[vitormhenrique]

yes, they do, touch test_file.py create and show the file on the file explorer, however, same behavior for Source Control screen, it does not show up any changes over there.

[joaomoreno]

Can't repro this on WSL at all.

[bpasero]

@joaomoreno fyi (because I have seen the code recently), could this be related to the check you do in git land if the window is focused or not? I noticed (in the web) that I was hard coding the window focus to false and nothing was working. Just wondering if remote extension could suffer from the same issue.

[mcpower]

I can reproduce the issue. This problem seems to be due to symlinks in the repository path:

$ git init repo
Initialized empty Git repository in /home/mcpower/vscode-no-changes/repo/.git/
$ ln -s repo symlinked-repo
$ touch repo/file
$ code repo  # shows "file" as being new
$ code symlinked-repo  # does not show "file" as being new

As a workaround, you can run code in the non-symlinked path (using realpath or similar utilities).

Windows 10 1803 with Ubuntu 18.04 running under WSL.
VS Code Stable version 1.35.0.
"Remote - WSL" version 0.38.0.
"Remote Development" version 0.15.0.

[ryansully]

This seems to be related to https://github.com/microsoft/vscode/issues/5970.

[joaomoreno]

@vitormhenrique:

1. Do you have symlinks at all?
2. Can you still repro this on the latest Insider builds?

[DavidASolis]

I can reproduce this issue. I am opening the repo via a symlink to /mnt/c/... As well as, I have several symlinks with relative paths in the repo itself.

[vitormhenrique]

Yes!

I do have syslinks!!

[joaomoreno]

https://github.com/microsoft/vscode/issues/5970