Skip to content

Conversation

@Zentrik
Copy link

@Zentrik Zentrik commented Jan 6, 2026

Should fix #916, but getting this installed locally seemed sufficiently complicated that I gave up. I figured out the nox stuff, I tested with two windows and this worked.
Fix is:

  1. Only watch a specific endpoint file
  2. Make sure this endpoint file is unique (I imagine the workspace file path can be non unique across vscode windows)

Should fix microsoft#916, but getting this installed locally seemed sufficiently complicated that I gave up.
Fix is:
1. Only watch a specific endpoint file
2. Make sure this endpoint file is unique (I imagine the workspace file path can be non unique across vscode windows)
rchiodo
rchiodo previously approved these changes Jan 8, 2026
@rchiodo rchiodo added the bug Issue identified by VS Code Team member as probable bug label Jan 8, 2026
@rchiodo rchiodo closed this Jan 8, 2026
@rchiodo rchiodo reopened this Jan 8, 2026
@rchiodo
Copy link
Contributor

rchiodo commented Jan 8, 2026

Whoops, didn't meant to close this. @Zentrik it looks like this is causing a bunch of test failures.

I guess this is what I get for trusting AI at midnight.
The error seems to be that `base` is `c:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\.noConfigDebugAdapterEndpoints` but `noConfigEndpointDir` is `C:\Users\RUNNER~1\AppData\Local\Temp\.noConfigDebugAdapterEndpoints` (the C is capitalised). Getting the fsPath of the URI should normalise the path the same as `base`.
@Zentrik
Copy link
Author

Zentrik commented Jan 9, 2026

@Zentrik it looks like this is causing a bunch of test failures.

Sorry about that, thanks for reviewing. I think it should be fixed now, o/w will have to wait till tmrw and I'll boot into windows to debug further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Issue identified by VS Code Team member as probable bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

No Config Debugging errors when multiple vscode windows are open

2 participants