Skip to content
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

Uncaught (in promise) Error: Looks like the language server is talking to long to respond, prease try again in sometime. #12460

Closed
monaka opened this issue Jan 18, 2019 · 4 comments
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.

Comments

@monaka
Copy link
Member

monaka commented Jan 18, 2019

Description

Sometimes I got error Uncaught (in promise) Error: Looks like the language server is talking to long to respond, prease try again in sometime.
I'm not sure whether it is reproductive on all environment. It is just for information.

Reproduction Steps

Creates workspace with Che-in-Che.
Starts it.

OS and version:

6.18.0-SNAPSHOT (with some my patches)
Azure AKS (B2s instance)

Diagnostics:

screenshot 2019-01-18 at 10 09 43

@ghost
Copy link

ghost commented Jan 23, 2019

@monaka can this be a random networking issue? Does it happen to any particular language server?

@ghost ghost added the kind/question Questions that haven't been identified as being feature requests or bugs. label Jan 23, 2019
@monaka
Copy link
Member Author

monaka commented Feb 2, 2019

@eivantsov My browser doesn't communicate with any language servers directly if my understanding is sure. So I guess it is not caused by unstable WAN network. And I believe the network in Azure is enough stable.

@ghost
Copy link

ghost commented Feb 2, 2019

@monaka nit directly to LS but via a workspace agent (websocket though).

In any case, i'd recommend trying a Che 7 workspace with TypeScript and Java language plugins onboard

@monaka
Copy link
Member Author

monaka commented Feb 12, 2019

This may fixed after I changed my ingress to Traefik (refs #12645).
I close it for now. (might re-open if I could reproduce it.)

@eivantsov I agree Che 7 is the better choice for the future.
But I'm blocked by #12585 on GWT-IDE and waiting to be implemented GIt related features on Theia. :-)

@monaka monaka closed this as completed Feb 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Questions that haven't been identified as being feature requests or bugs.
Projects
None yet
Development

No branches or pull requests

1 participant