Looks like there’s a problem with 0.18.0 and mason.nvim.
AndyL
zachdaniel
Creator of Ash
ElixirLS has felt much more stable in recent releases, and I’ve not had to fight with new versions for the Spark plugin (which backs Ash’s DSL tooling). Thanks for all your hard work!
15
lukaszsamson
ElixirLS Core Team
Version 0.19.0 has been released 
Highlights:
- On type parsing and diagnostics for phoenix
.heexfiles - Workspace symbols provider has been reimplemented. Previously the workspace symbols index was build from all available symbols. To make it more focused and helpful now only symbols from the project are considered. This change made it much quicker and improved the quality of returned results. Fuzzy matching engine was also improved and made consistent with how complete provider works.
- [VSCode] Test UI is now able to run multiple tests at once. This is made possible with running
mix testcommand via debug adapter with a custom ExUnit formatter streaming test suite progress via DAP output events. Running multiple tests is supported on workspace folder, file, module, describe blocka and doctest level
See full release notes
ElixirLS elixir-ls/CHANGELOG.md at v0.19.0 · elixir-lsp/elixir-ls · GitHub
vscode extension vscode-elixir-ls/CHANGELOG.md at v0.19.0 · elixir-lsp/vscode-elixir-ls · GitHub
23
dimitarvp
This is very welcome. It was detracting from the usefulness of the tool. Glad to see it addressed.
arcanemachine
This release seems much more responsive that previous ones.
Thanks for your hard work, ElixirLS team!
jbosse
Did token scopes change again with 19 or the Jan vscode update? My theme is unpleasant again. 
lukaszsamson
ElixirLS Core Team
There were 2 changes:
do-endand<<>>bracket matching landed. It can be disabled witheditor.bracketPairColorization.enabled: falseor configured witheditor.language.colorizedBracketPairs, see Syntax highlighting broken in "Darcula theme for Elixir" · Issue #404 · elixir-lsp/vscode-elixir-ls · GitHub- Invalid scope assigned to charlists has been fixed
nhpip
Hi,
I recently upgraded to vscode 1.86.1 and all of a sudden the beam VM that vscode starts randomly hits 500% or more CPU. It’s been running great until I upgraded.
Any ideas?
Here are my specs:
Erlang: 26.2.1
Elixir: 1.16.0-otp-26
VcCode: 1.86.1
ElixirLS: v0.19.0
MacOS: ventura 13.5
jbosse
Thanks for the reply. I don’t think this wouldn’t account for the changes in my theme. I will have to figure out if it is my overrides I added for 1.17. Maybe. VSCode changed something. That updated for me yesterday as well. :-/
lukaszsamson
ElixirLS Core Team
Have you tried connecting with observer to see what going on? You can pass name/sname/cookie via `ELS_ELIXIR_OPTS’