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

[ JDT LS ] The progress of language server resolving doesn't displayed in the bottom status bar #11481

Closed
Ohrimenko1988 opened this issue Oct 4, 2018 · 2 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@Ohrimenko1988
Copy link
Contributor

Ohrimenko1988 commented Oct 4, 2018

Note
The bug is actual for this assembly:
#10863

Description:
Do not meet expectations according to this issue:
#8412
screenshot from 2018-10-04 15-02-13

Reproduction Steps

  • Deploy JDT LS assembly
  • Start default "java" stack with default "spring" project
  • Wait until workspace is started
  • Wait for maven progress bar disappearance
  • Pay attention to the terminal output and bottom status bar

Expected behavior:
The progress bar of the language server starting is displayed in the bottom status bar

Observed behavior
The language server is starting (according to the terminal output) but the progress bar doesn't display

Attachment:
hhhhh

Browser terminal output
gggfgfg

OS and version:
JDT LS assembly Che 6.12.0 ; Chrome 68; hedora 28

@Ohrimenko1988 Ohrimenko1988 added kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. team/languages labels Oct 4, 2018
@tsmaeder
Copy link
Contributor

tsmaeder commented Oct 8, 2018

Yes, this is the expected behaviour: jdt.ls does not send progress messages for startup, it sends status messages, which are not expected to be progress.

@che-bot
Copy link
Contributor

che-bot commented Sep 7, 2019

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2019
@che-bot che-bot closed this as completed Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants