lemma-osu / naip-cnn

Modeling forest attributes from aerial imagery using CNNs
0 stars 0 forks source link

Source control not auto-refreshing in VS Code #8

Closed aazuspan closed 9 months ago

aazuspan commented 1 year ago

When running the project in a Docker container in WSL, changes are not automatically detected by source control in VS Code, despite being detected by git status. Manually refreshing Source Control seems to resolve the issue.

This definitely isn't a unique issue (see this and this and this), but my current guess is that this is an unrelated bug caused by VS Code watching a different folder than we're working on due to how I set up the Docker mounting.

Things that haven't worked:

aazuspan commented 11 months ago

Quick update: I did a little more testing and have the same issue even when using a base container generated by VSCode, which suggests it's probably not an issue with the Docker config.

Interestingly, source control does register changes when using the official sample dev containers. The difference between that and the base container or the naip-cnn container is that it's a remote repository that only exists in the Docker filesystem, rather than a local repository that's mounted into Docker, so maybe that's a hint... Next step, try the naip-cnn container on a Linux machine, since I'm suspicious that this is a Windows/WSL problem.

aazuspan commented 10 months ago

This also seems to impact DVC experiment tracking (#20), but unlike with git this can't be resolved by manually refreshing.

More evidence from microsoft/vscode-remote-release#9399 suggests this is a WSL/Windows issue:

The Source Control view refreshes based on file-system events and there are various known issues where file system events are not delivered when files are stored in the Windows file system.

I tried a few workarounds from that thread with no luck: