Julia Language Error

1

Hello. I received an influx of emails from students saying that they started to receive the below error.

Error while communicating with the LS. Check Output > Julia Language Server for additional information.

We’ve been able to trouble shoot most students using the below solution, but not all seem to be able to resolve with this method. Any suggestions would be greatly appreciated. I would also recommend Pumas send an email to all current users for greater visibility, as this seems to be a universal issue.

Current solution:

  1. Go to your Julia Extensions, select the cog wheel (settings), and select “Install Specific Version”. Then select version “1.124.2”.
  2. Enable Inline Code Execution if this change is still not letting you run line-by-line. To do so, Open Settings (click “Ctrl” and “,” at the same time), and search for “Execute in REPL” under the Julia extension settings to ensure it’s enabled (see below). This setting directs code execution to the REPL when you use shortcuts like Shift-Enter. Restart VSCode after updating this as well.
2

Thanks for bringing this up here and for sharing the workarounds. It seems like a new version of the Julia extension for VS Code was released over the weekend and that this version has some compatibility issues with Julia 1.9 which is what Pumas 2.5.1 is based on. I have been able to trigger the same error when using Julia 1.9 without Pumas.

I would think that downgrading the version of the extension as you mention in 1. would be sufficient if you restart your Julia session. Are you certain the 2. is required?

1 Like
3

Ok good to know. Regarding Part 2 it seems that when the automatic update happened it changed this setting. I actually also experienced this when I allowed Julia to update, as well as most students
I talked with. If you want to continue to run Inline Code Execution (Ctrl+Enter, etc.) then it is necessary. Highlighting chunks of code and running seemed to continue to work, however. I’m not sure why that is the case.

4

Thanks for details. It is very helpful. We are in contact with the maintainer of the extension to try to understand why this is happening. I will provide an update once we know more.

2 Likes