Skip to content

Upgrade language server protocol to v3.2.0 #445

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

Merged
merged 54 commits into from
May 2, 2017
Merged

Upgrade language server protocol to v3.2.0 #445

merged 54 commits into from
May 2, 2017

Conversation

kapilmb
Copy link

@kapilmb kapilmb commented Apr 27, 2017

No description provided.

Kapil Borle added 30 commits April 19, 2017 19:48
Whenever EditorServices fails to start up, ServerTestsBase.LaunchService goes into a while loop where it reads from the error stream line by line in an async manner, till the end of the stream. This causes the method to wait indefinitely in certain situations. Hence, we replace it with ReadToEndAsync method and time out on the task if it takes too long. This avoids the test cases from hanging at that point.
@kapilmb
Copy link
Author

kapilmb commented Apr 28, 2017

Looks like I missed some types. I think this PR should be ready tomorrow.

@kapilmb kapilmb changed the title [WIP] Upgrade language server protocol to v3.2.0 Upgrade language server protocol to v3.2.0 Apr 29, 2017
@kapilmb
Copy link
Author

kapilmb commented Apr 29, 2017

This PR is finally ready to be reviewed!

@daviwil
Copy link
Contributor

daviwil commented May 2, 2017

Excellent work man, thanks a lot! I just tried out this PR and the VS Code one on my machine, works great!

@daviwil daviwil merged commit 81d570f into develop May 2, 2017
@daviwil daviwil deleted the kapilmb/lsp-3 branch May 2, 2017 01:16
@kapilmb
Copy link
Author

kapilmb commented May 2, 2017

Thanks @daviwil !

@daviwil daviwil modified the milestone: 1.0.0-beta.1 May 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants