Benjamin Pasero

Ok, if you see this again and can distill steps, that would be great. Maybe some setting got synced that caused this.

I believe the native dialog would refuse to accept an invalid path that does not exist, so I think the simple dialog could do the same. But I worry that...

I think its probably best to do some kind of validation at these methods: https://github.com/microsoft/vscode/blob/4cec36a9d9bdfa4312921e8eb5e6b5c60f82c577/src/vs/workbench/services/dialogs/browser/abstractFileDialogService.ts#L60 https://github.com/microsoft/vscode/blob/4cec36a9d9bdfa4312921e8eb5e6b5c60f82c577/src/vs/workbench/services/dialogs/browser/abstractFileDialogService.ts#L79 And not do it in each component that asks for this path. Treating as...

I can still reproduce with latest insiders.

I think this is https://github.com/electron/electron/issues/37789 with an associated PR https://github.com/electron/electron/pull/38208

@deepak1556 isn't there support from Electron to do this? Anything that would speak against using it? From https://github.com/electron/electron/blob/main/docs/api/app.md 

One thing to keep in mind is that we have lots of scenarios where we would not want such a dialog, for example CI smoke test runs or VS Code...

Reported as upstream, its likely that the OS watcher methods (`ReadDirectoryChangesW`, `fsevents`) are not even providing this information so its hard to workaround this: https://github.com/parcel-bundler/watcher/issues/185

I am closing this issue, given the reported upstream. As we stay with parcel watcher, fixes have to go there and we are actively contributing.

/gifPlease