LSP4IJ 0.17.0 Release #1305
Replies: 3 comments 11 replies
-
|
@angelozerr With a recent build (
|
Beta Was this translation helpful? Give feedback.
-
|
I did a quick smoke test on the Docker side and it seems okay for LSP and DAP. I created a pull request (#1315) to have the documentation explicitly ask the user to set the environment variable since it does not seem like #1298 is fully fixed at the moment. Thanks for the great work as always, Angelo! |
Beta Was this translation helpful? Give feedback.
-
|
LSP4IJ 0.17.0 release is now available on JetBrains marketplace ! |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are about to release LSP4IJ 0.17.0. Highlights of this release include
But the main important change is #1303 which should fix a lot of issues with start/stop, restart language server where the stop could stop the restart language server if server takes some times to shutdown for instance. This PR should take care of the awful
Missing header Content-Length in input ...error which can occur and in this case you need to close and reopen your IJ (so bad). I have not found a usecase to have this error but I can emulate it and now LSP4IJ should take care of thisMissing header Content-Length in input ...error by stopping and restarting the server instead of closing your IJ.I had to do a big change so please test your plugin by starting, stopping, restarting, stopping again and restart again and again to check it continues to work, in short try to stress this start/stop server. You can stop server with Action or if you close all files.
Please also note that highlighting is broken in 2025.2 #1300 because JetBrains seems having changed the behavior of
HighlightUsagesHandlerFactory. I am debugging 2025.2 to try to find a fix but I don't know if I will find a solution. I will try to do my best to fix it before the release but I cannot promise you thatbut I suspect that it is a bug from IntelliJ #1300 (comment). We need to wait a new version of JetBrains to test it.More details in the changelog.
Please give a try to the latest nightly build.
Unless you report a blocking issue, we'll proceed with the release next Monday 10/06/2025. If you need to have more time, please tell me.
cc @CppCXY @InSyncWithFoo @seachicken @KUGDev @AlexWeinstein92 @aparnamichael @MituuZ @turkeylurkey @mrglavas @koxudaxi @FalsePattern @onriv @kristofvb @kdvolder @rcjsuen @jansorg @SCWells72 @ericdallo @nikunjarora12345 @DetachHead @sergeysavchuk @bzoracler @bratorange
Beta Was this translation helpful? Give feedback.
All reactions