-
Notifications
You must be signed in to change notification settings - Fork 409
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
Provide Progress Notification #404
Comments
45 tasks
3 tasks
There is a WIP PR here: #490 |
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Mar 19, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Mar 20, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Mar 20, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Mar 20, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Mar 20, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
fbricon
added a commit
to fbricon/eclipse.jdt.ls
that referenced
this issue
Mar 20, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
tsmaeder
pushed a commit
to bdshadow/eclipse.jdt.ls
that referenced
this issue
Apr 6, 2018
Fixes eclipse-jdtls#404 Signed-off-by: Fred Bricon <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
jdt.ls does a bunch of long running tasks (build, update maven project, indexing jars, etc.) that can result in high system load and affect outcomes of stuff like content assist.
These tasks may be done in response to a LSP request or notification or they may be triggered by jdt.ls itself.
We should have a way to report progress to the client. Some of the issues that need to be addressed are:
Progress reporting is for humans: more than 2-3 notifications/second cannot be seen anyway.
The text was updated successfully, but these errors were encountered: