Configuration values are missing from files on remote network drives

[RobIsHere]

When I open a folder from my server e.g. \MYSERVER\some-project, all debug configurations are missing.

If I open the same folder from a drive letter, that is mapped to \MYSERVER\some-project, all debug configurations work as expected.

==================================

• VSCode Version: Code 1.14.2 (cb82feb, 2017-07-19T23:34:09.706Z)
• OS Version: Windows_NT ia32 10.0.14393
• Extensions:
  vsc-ember-frost|cie|0.0.2
  vscode-eslint|dba|1.2.11
  vscode-babel-coloring|dza|0.0.4
  redux-snippets|jam|0.0.2
  debugger-for-chrome|msj|3.1.6
  code-settings-sync|Sha|2.8.2
  vscode-react-native|vsm|0.4.0

Reproduces without extensions: Yes

[isidorn]

This is due to the fact that we are missing file events from network locations. So debug does not get pinged by configuration service for a change
Forwarding to @bpasero since he probably knows if this is a duplicate or this should be covered by #13665

[RobIsHere]

To clarify this: I did not change the launch.json. The launch.json was like today for at least a month, working well.

But vscode always deletes the Recent Folder Entry, when you forget to click on the drive-mapped network folder in explorer.

So I decided to open it via its network name. But then I can't debug.

As this incident happened at the same time with some other issues and updates, I wasted two hours to find the cause. At least please add this to an FAQ or docs.

[isidorn]

Thanks for more details.
FYI we accept PRs for vscode-docs here https://github.com/microsoft/vscode-docs

[se-m]

Problem exists even you mount network shares to folders
e.g. mklink /d c:\proj \\server\share\foldername\

vscode does not read not only debug config (launch.json), but also workspace settings (settings.json)

[bpasero]

@RobIsHere do the configurations show up when you do a restart of VS Code? If not, then this imho is not a file watching problem.

[RobIsHere]

I share your opinion. I restarted it a couple of times and they never showed up.

Unless you have done very unusual things in your code, this is no file watching problem. But that's what I already wrote above.

I'm on sailing holiday, so I can't do further testing now, sorry

[bpasero]

Ok thanks, we should try to reproduce this somehow. I have heard issues like that in the past.

[bpasero]

Does this still happen?

[RobIsHere]

Yes. Version 1.18.0. In the screenshots below you can see one and only one project.
Its located on my MacBook. And shared from there via SMB.

When opened remote from my Windows 10 PC, You see the debug configs are missing (Keine Konfigurationen = No Configurations) and there is an indicator to work on the debug configs. Although the commands can be executed via shell.

Having this working would be quite cool, because the ios simulator only runs on a mac. So I would like to ssh-tunnel the react-native packager to the mac.

[bpasero]

@RobIsHere @se-m would you be willing to help out on this issue by setting up VS Code to run from its sources so that we can add some debug information? The steps how to get there are outlined here: https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source

[RobIsHere]

Narrowed it down to https://github.com/Microsoft/vscode/blob/master/src/vs/base/common/paths.ts#L24

Run the function with

from = "\\ROBERTS-MBP\Dropfella", to = "\\ROBERTS-MBP\Dropfella\.vscode\launch.json"

and you get

Return value "../..//ROBERTS-MBP/Dropfella/.vscode/launch.json"

[RobIsHere]

https://github.com/Microsoft/vscode/blob/master/src/vs/base/common/paths.ts#L167
calling getRoot("\ROBERTS-MBP\Dropfella") returns "/"
calling getRoot on some subfolder works

So a comparison of the two roots is not equal.

See the screenshots:

[bpasero]

@RobIsHere great work, can you grab latest from master and see if the fix I pushed makes it any better?

@jrieken it looks like path.relative('\\\\ROBERTS-MBP\\Dropfella', '\\\\ROBERTS-MBP\\Dropfella\\.vscode\\launch.json') results in ../..//ROBERTS-MBP/Dropfella/.vscode/launch.json. We need to either fix that method or use the node.js one. The problem is that all remaining clients of our paths.relative live in common (including glob.ts)...

[jrieken]

I am not responsible for path.relative not a single line of my code has survived there and "yes" it's completely broken because it doesn't respect the root of a path. Use node-path whenever possible, ideally move all code to /node/ if it requires path-math.

[RobIsHere]

The debug configurations don't appear.

The sourcemaps seem to be broken now, breakpoints stop on different rows than the one I'm targeting, so it's tedious to find it out.

Maybe tests of some of the involved methods could be a lot faster in dev time than try-and-error?

Just another thing, don't know if that's a problem: getRoot is e.g. also called from paths.normalize:
return paths.normalize(relative(this.folder.fsPath, resource.fsPath), toOSPath);
So I'm not 100% sure about the fix.

[bpasero]

@RobIsHere I think I am able to reproduce now when I use the UNC localhost notation on Windows and open the root drive with a .vscode folder inside: \\localhost\c$. However after my fix I see the configurations showing up, and without they do not.

To be on the safe side can you maybe try to reproduce with todays insider build that includes my fix? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

[bpasero]

Closing for November, this should be fine now.

[RobIsHere]

I think this is not working yet!

[bpasero]

@RobIsHere can you use insiders please, the screenshot looks like you are still running out of sources.

[se-m]

Hi.
I checked the last one insiders build. On windows 7x64 all fine. Debug configuration appears. There is no watch and autoreload, so you should restart vscode (or close&open folder) to see your changes in configuration file, but its ok.
Tested in both variants: "network shares as folders" and "network shares as network drive"

Version 1.19.0-insider
commit 3afa334

[RobIsHere]

Can you install and run insider build side by side with the "normal" build? I'm hesitating a little bit because I still need my dev machine at work ;)

[se-m]

Get latest code from github (commit bce608e) and make it run. Configuration also appears.

[se-m]

[se-m]

left normal build 1.18.0
center build from sources
right insider

the same folder is open in all three

[RobIsHere]

Your github is showing 14 changes. But doesn't show any in insiders or master.

At my machine (accessing a smb share on mac from windows) it's the opposite. I'm seeing my github changes only on the master branch, not in the normal build.

Could this also be related to the changed path resolution here?

[se-m]

My git installation folder not in usual place. I set up "git.path" param and it show the same result (14)

[bpasero]

@se-m great to hear. yeah file events might be broken in that setup, that is a known issue. Closing as fixed.

[RobIsHere]

Thank you @bpasero! I can confirm that this works in the insider build.

( It still does not work on master branch. But because you already had this in mind, this is probably specific to your git workflow )

[dbaeumer]

Marking as verified due to #31667 (comment)