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
Remove random port detection #274
Milestone
Comments
jpogran
added a commit
to jpogran/puppet-vscode
that referenced
this issue
Jun 21, 2018
This commit removes the code that detects and uses a random port for the LanguageServer to run on. It instead parses the STDOUT message from the LanguageServer for the port it is running on and uses that to connect. If the user sets a port in the config, that is used instead of reading the port from the LanguageServer.
jpogran
added a commit
to jpogran/puppet-vscode
that referenced
this issue
Jun 21, 2018
This commit removes the code that detects and uses a random port for the LanguageServer to run on. It instead parses the STDOUT message from the LanguageServer for the port it is running on and uses that to connect. If the user sets a port in the config, that is used instead of reading the port from the LanguageServer.
jpogran
added a commit
to jpogran/puppet-vscode
that referenced
this issue
Jun 22, 2018
This commit removes the code that detects and uses a random port for the LanguageServer to run on. It instead parses the STDOUT message from the LanguageServer for the port it is running on and uses that to connect. If the user sets a port in the config, that is used instead of reading the port from the LanguageServer.
glennsarti
added a commit
that referenced
this issue
Jun 26, 2018
(GH-274) Remove random port detection
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the extension determines a random unused port in order to communicate with the language server over tcp. In PR #279 stdio will become the default protocol, meaning using tcp will be mostly used by those doing advanced scenarios where they will be picking the host name and port and won't want something attempting to pick a port for them.
This issue suggests we remove the random port detection and rely on the configured port to connect if using tcp. This would avoid some of the problems in #240, while also addressing some of it.
The text was updated successfully, but these errors were encountered: