-
-
Notifications
You must be signed in to change notification settings - Fork 501
Description
This might be related to #3928 in that it might be a windows only issue, I won't be able to test on Linux for a couple days. The named pipe JSON file never seems to be created when the extension is executed from inside VS Code - like when you are trying to develop and/or debug the extension.
The named pipe JSON file is created when the extension is used normally. But if I delete it from my AppData folder and then run the extension under VS Code development, it does not get re-created.
I tried setting a VS Code breakpoint in startNamedPipeServer but it never seems to resolve the breakpoint, even after attaching to the language server. So there must be some other piece I would need to attach to in order to step through that code.
I am assuming this named pipe issue is why it can't contact the language server and thus why everything comes up red.
Note: This was discovered while trying to debug custom extensions being broken in the 2.x release. I will open a new issue for that and see if I can debug that further under Linux.
