microsoft / microsoft/vscode-remote-release

Bug Report: Folder Not Refreshing Over SSH Remote Connection

Open
#11,504 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ssh
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

I am connected to another computer via SSH using VS Code Remote – SSH.

I have a script that creates files inside folders. If I open one of these folders in VS Code while the script is still running, but before the files are created (so the folder is empty at the time I open it), the folder remains empty in the Explorer even after the script finishes and the files have been successfully created.

There is no automatic refresh of the folder when the script finishes.

Important Details
  • This happens only when connected via Remote – SSH.
  • This does not happen when using a WSL connection.
  • If I close and reopen the folder, the files still do not appear.
  • The only ways to make the files show up are:
    • Restart VS Code
    • Manually create a new file in the folder (which triggers a refresh)

It seems like the file watcher does not detect file creations in a folder that was opened while empty during an SSH remote session.

Please let me know if additional logs or reproduction steps would help.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with VS Code Remote–SSH: open an empty folder while a script is running, then let the script create files. Compare the behavior with a WSL connection and check whether the remote file watcher reports the creations. Done means newly created files appear in Explorer without restarting VS Code or manually creating another file.

Written by the indexing model from the issue text.

Assessment

Tech stack
vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.