microsoft / microsoft/vscode-remote-release

Ignored files & folders are unreliably greyed out in file explorer

Open
#11,294 0 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

bug file-explorer
Dominant language
Dockerfile
Stars
4.2k
Forks
469
Avg merge
1d 1h
Merged PRs (30d)
1

Description

  • VSCode Version: 1.105.1
  • Local OS Version: Ubuntu 22.04
  • Remote OS Version: Docker image based on Ubuntu 22.04
  • Remote Extension/Connection Type: Dev Containers

Steps to Reproduce:

  1. Work in a dev container, with a project containing a .gitignore file.
  2. Sometimes, some ignored files/folders are not greyed out in the file explorer.
  3. Simply re-save .gitignore triggers a refresh and all ignored files/folders are now greyed out.
  • First screenshot: some ignored files and folders are not greyed out.
  • Second screenshot: just after re-saving .gitignore (not changing anything in it – only pressing Ctrl-S), all ignored files and folders are greyed out correctly.
Image Image

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
However it does occur when working in the dev container, with all extensions disabled. (Confirmed with extension bisect. Microsoft's Dev Containers was the only active extension.)

It doesn't appear to be related to a file watchers limit: the inotify limit is very high on my system, and modifications made in my OS's file explorer are instantly reflected in VS Code's file explorer.

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.