No Config Debugging errors when multiple vscode windows are open

[Zentrik]

If I use the no config debugging feature with multiple vscode windows open, all of them try to start debugging. Whichever is first suceeds and the rest throw a Server[pid=xxxx] is already being debugged error.

The cause for this is that the extension watches the .noConfigDebugAdapterEndpoints dir and starts debugging if any file appears in it not just if the specified file (VSCODE_DEBUGPY_ADAPTER_ENDPOINTS) is created. Each window has a separate endpoint file in the .noConfigDebugAdapterEndpoints dir, but due to watching for any file, every window will start debugging.

vscode-python-debugger/src/extension/noConfigDebugInit.ts

Lines 95 to 97 in d7b9643

	// create file system watcher for the debuggerAdapterEndpointFolder for when the communication port is written
	const fileSystemWatcher = createFileSystemWatcher(new RelativePattern(tempDirPath, '**/*.txt'));
	const fileCreationEvent = fileSystemWatcher.onDidCreate(async (uri) => {

[Zentrik]

Looks like #592 and #632 were due to this as well

[eleanorjboyd]

Hi! This is a known limitation of the no-config debugging. Due to its implementation, it does not allow for multiple at once. You could submit a feature request if this is a feature you would want but right now it is out of scope as bug report. Thanks

[Zentrik]

Ok, if it's not too much trouble I think it would be nice to document this e.g. on the wiki page or perhaps you might want to take a look at #918 which implements this feature.
Thanks.

[eleanorjboyd]

great point thank you!

[rchiodo]

Reopening until this ships