file explorer is not updated after a git pull

[jeremy447]

Hello,

I noticed that sometimes the file explorer doesn't get updated (missing folder at least) after making a git pull (from external terminal).

• VSCode Version: 1.11.1
• OS Version: Fedora 25

Thanks !

[bpasero]

@Paviluf which folder specifically would not update? Can you share your settings?

[jeremy447]

It's the folder highlighted that wasn't there after a git pull. I checked in nautilus (file explorer) and it was there. I rebooted Vs Code and the folder was available.

Here is my settings :

{
  "editor.fontSize": 13,
  "editor.fontFamily": "Droid Sans Mono",
  "editor.tabSize": 2,
  "editor.detectIndentation": false,
  "editor.renderIndentGuides": true,
  "editor.wordWrap": "on",
  "editor.rulers": [80],
  "workbench.iconTheme": "vs-seti",
  "workbench.welcome.enabled": false,
  "editor.minimap.enabled": true,
  "editor.minimap.renderCharacters": false,
}

[bpasero]

@Paviluf does it show up when you refresh the explorer using the little refresh icon?

[jeremy447]

I can't tell since I restarted vscode and the folder was there. If it happen again I will try.

[jeremy447]

It happened again. If I refresh the explorer using the little refresh icon it seem to refresh only the subdirectory where I'm.

[jeremy447]

I think it always happen when someone else create a new folder (files ?) and you fetch it with git pull.

[jeremy447]

Very annoying bug. I hope it can be fixed for april release :)

[jeremy447]

My coworker have the same problem on Ubuntu 16.04

[bpasero]

Please see if you can find any logged output that could help us find the source of the issue:

• run code --verbose from the command line and attach the output
• in Code select Help | Toggle Developer Tools and select the Console
• attach any output you see in the Console you can find

Thanks!

[jeremy447]

Well I made some tests after updating to 1.12 and it didn't happen. I will continue my tests and if it doesn't happen anymore I will close the issue.

[bpasero]

@Paviluf this would indicate to me that the bug is some race condition and unreliable to reproduce, which is odd, but quite possible for these kind of issues. In the end the OS might decide to not send around file changes in certain cases or we fail to read them in certain cases.

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.