Closed fenollp closed 3 weeks ago
LSP version: _
This missing information is crutial actually.
reloading plugin LSP-rust-analyzer.plugin_commands ModuleNotFoundError: No module named 'LSP'
That looks like your LSP is still running on py33.
LSP package might have gotten ignored on updating. Check if it's in ignored_packages
in ST Preferences and remove if so.
This missing information is crutial actually.
Well, I'm sure you see the Catch-22 here ;)
Thanks for putting me in the right direction! It seems indeed related to the move to py38, which is mentioned in the release notes. However upgrade somehow failed so I could not read these release notes...
Anyway, now I have a direction to dig through! Thanks :)
NOTE: Is there a dependency on node
? Also, this mentions windows.py? I'm on Linux and never use node
nor want to.
plugins loaded
Package Control: Removed orphaned library "sublime_lib" for Python 3.3
Package Control: Removed orphaned library "lsp_utils" for Python 3.3
Package Control: All specified packages up-to-date!
reloading /home/pete/wefwefwef/rustcbuildx.git/src/cli.rs
...SNIP...
Unable to open /home/pete/wefwefwef/rustcbuildx.git/src/extensions.rs
reloading /home/pete/wefwefwef/rustcbuildx.git/src/runner.rs
...SNIP...
--- lsp_utils Node.js resolving start ---
Resolving Node.js Runtime in env PATH for package LSP-bash...
* Failed: "node" binary not found
Resolving Node.js Runtime from lsp_utils for package LSP-bash...
* Binaries check failed: "node" binary not found
* Download skipped
--- lsp_utils Node.js resolving end ---
Unable to start subprocess for LSP-bash
Traceback (most recent call last):
File "/home/pete/.config/sublime-text/Installed Packages/LSP.sublime-package/plugin/core/windows.py", line 256, in start_async
if plugin_class.needs_update_or_installation():
File "/home/pete/.config/sublime-text/Lib/python38/lsp_utils/_client_handler/abstract_plugin.py", line 101, in needs_update_or_installation
server = cls.get_server()
File "/home/pete/.config/sublime-text/Lib/python38/lsp_utils/npm_client_handler.py", line 122, in get_server
cls.__server = ServerNpmResource.create({
File "/home/pete/.config/sublime-text/Lib/python38/lsp_utils/server_npm_resource.py", line 47, in create
node_runtime = NodeRuntime.get(package_name, storage_path, required_node_version)
File "/home/pete/.config/sublime-text/Lib/python38/lsp_utils/node_runtime.py", line 59, in get
cls._node_runtime = cls._resolve_node_runtime(package_name, storage_path, required_semantic_version)
File "/home/pete/.config/sublime-text/Lib/python38/lsp_utils/node_runtime.py", line 129, in _resolve_node_runtime
raise Exception('Failed resolving Node.js Runtime. Please check in the console for more details.')
Exception: Failed resolving Node.js Runtime. Please check in the console for more details.
Does this require node/npm? README doesn't mention that
Does this require node/npm? README doesn't mention that
LSP-bash required node.js indeed. Either you have a compatible system installation, or an installation managed by lsp_utils, which I guess has been rejected by you (Download skipped).
enabled/disabled some packages, reinstalled lsp and lsp-ra and all good! Thanks!
Describe the bug
Recently, my installed LSP package disappeared. Today, installing it though the command pallette is impossible:
LSP
doesn't shows up in the results of the querylsp
.Reinstalling other LSP packages e.g. Rust's seems to work, until it fails on the missing dependent LSP base package:
To Reproduce
Steps to reproduce the behavior:
lsp
in the command palette (Install package...)Expected behavior
I'd expect either of these:
LSP-bare-minimum
Environment (please complete the following information):