[Extension] Download rust-analyzer server stuck 100%
See original GitHub issue- Web Browser: Chrome 83.0.4103.97
- Local OS: Windows 10 2004
- Remote OS: Ubuntu 20.04 LTS
- Remote Architecture: amd64
code-server --version
: 3.4.1 48f7c2724827e526eeaa6c2c151c520f48a61259
I waiting for 2 hours, no response, no log.
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (7 by maintainers)
Top Results From Across the Web
[Extension] Download rust-analyzer server stuck 100%
I had previously worked around this by setting the rust-analyzer.serverPath to the location that code-server stores the binary in, ...
Read more >rust-analyzer
rust -analyzer is an implementation of Language Server Protocol for the Rust programming language. It provides features like completion and goto definition for ......
Read more >rust cargo blocking waiting for file lock on package cache
I got the same problem. I am using Linux and this is how to solve it: Close VS Code so that the the...
Read more >Is it just me or rust-analyzer is unreliable/slow?
You won't get some macro-related completions, but it might be a lot more reliable. Make sure you're running the latest release of the...
Read more >Proc macro support in rust-analyzer for nightly rustc versions
And identifiers, for example, are "interned" by the proc-macro server. If you have the identifier "foo" a hundred times, you don't pass around...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, guys, the author of the workaround in rust-analyzer here 😄 I’ll just add a small check for 13+ version of node before applying it. I didn’t know that the workaround does break the extension on newer versions (since vscode still uses v12)
Ahhh nevermind I was able to replicate on Node 14 which is what we ship with code-server. I was running with Node 12. It looks like the extension has a workaround for a bug in Node 12 but the bug is fixed in Node 13+ and the workaround ends up causing this bug instead. They have a note to remove the workaround once VS Code updates their Node version.
@nhooyr maybe we’ll need to target the same Node version VS Code uses after all. 😦