-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update language server to use named pipe client #6351
Conversation
|
||
// Wait for the server to send back the name of the pipe to connect to. | ||
_channel.appendLine('waiting for named pipe information from server...'); | ||
const pipeConnectionInfo = await namedPipeConnectionPromise; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably add a timeout here and show an error toast if it times out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes that's a good idea. Should probably do it for both receiving the name and making the named pipe connection
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Current communication between client and server is writing to STDOUT. This makes the connection vulnerable to any code in the process writing to stdout stream and corrupting the data.
This PR uses a named pipe...
NOTE: Need server PR to go in and then update the server version in this PR.
This has been tested on both windows and mac.