Network: Left side explore folders don't always open

[network211]

• VSCode Version:1.9.1
• OS Version: windows 7

Steps to Reproduce:
Don't know how to reproduce this consistently.

I can be editing along and want to go to a folder in the Explorer on the left.
I hit the folder name with the mouse. The caret changes from pointing right to pointing down, but the subfolder do not open. (see the 2 attached files, open and closed).

Click on folder. It is still closed, but now looks like this:

If I reload the folder and hit refresh, it seems to work

[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!

[network211]

I have attached a screenshot of the dev tools when running under verbose.

Toggling the folder does not add any entries to the console, The yellow warning appear at the top are caused by plugin Bookmark. I removed the plugin and restarted. The yellow warnings disappeared, but the toggle behavior is the same..

Here is a capture of the verbose login. I have removed duplicate entries related to file watcher.
console.txt

[bpasero]

@network211 is this some special file system? could you have some security tool running that maybe blocks Code from accessing the file system in a weird way?

[network211]

It is a networked mapped drive, a drive letter mapped to a share on another server within our local network.

…

-------- Original message -------- From: Benjamin Pasero <notifications@github.com> Date: 3/1/2017 23:35 (GMT-06:00) To: Microsoft/vscode <vscode@noreply.github.com> Cc: IT <IT@network211.com>, Mention <mention@noreply.github.com> Subject: Re: [Microsoft/vscode] Left side explore folders don't always open (#21520) @network211<https://github.com/network211> is this some special file system? could you have some security tool running that maybe blocks Code from accessing the file system in a weird way? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#21520 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AP4lznyq8bNgJ1xyBC4e2Qh512NdZ4d2ks5rhlUogaJpZM4MNlO1>.

[network211]

Also, when this happens, it doesn't happen for all folders. I.e., I can open other folders, just not certain ones.

[bpasero]

@network211 and you can use the command line to list the contents of these without errors?

[network211]

dir v:\classes dir v:\classes\local (that is the subfolder under classes) lists all correctly Or from git bash shell ll /v/classes/local lists all correctly. Also no problem when File | Open which uses the windows file open dialog Also no problem when Ctrl+E and then type the file name or path\filename From: Benjamin Pasero [mailto:notifications@github.com] Sent: Thursday, March 02, 2017 9:31 AM To: Microsoft/vscode <vscode@noreply.github.com> Cc: IT <IT@network211.com>; Mention <mention@noreply.github.com> Subject: Re: [Microsoft/vscode] Left side explore folders don't always open (#21520) @network211<https://github.com/network211> and you can use the command line to list the contents of these without errors? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#21520 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AP4lzsMW7UEQtbgNBuqXhS1YllTYLp4Oks5rhuCqgaJpZM4MNlO1>.

[bpasero]

Ok, sorry to tell that but I am out of ideas. Since this issue comes from node.js there does not seem to be a workaround.

[network211]

Thanks. I’ll see if I can determine how to reliably reproduce this issue (ie what steps) and post them. From: Benjamin Pasero [mailto:notifications@github.com] Sent: Thursday, March 02, 2017 9:40 AM To: Microsoft/vscode <vscode@noreply.github.com> Cc: IT <IT@network211.com>; Mention <mention@noreply.github.com> Subject: Re: [Microsoft/vscode] Left side explore folders don't always open (#21520) Ok, sorry to tell that but I am out of ideas. Since this issue comes from node.js there does not seem to be a workaround. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#21520 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AP4lznEQAVoXyvltHxjBbxeRdzpNpcUyks5rhuLlgaJpZM4MNlO1>.