Error when prompted to upgrade rust-analyzer
See original GitHub issueThe extension prompts me to download the newest rust-analyzer source from GitHub:
Rust Analyzer has a new release: 2020-06-08, you're using 2020-06-01.
Would you like to download from GitHub:
1. Yes
2. Check GitHub releases
3. Cancel
Type number and <Enter> or click with mouse (empty cancels):
However it gets stuck at 0.06% each time and throws the following error message:
[coc.nvim] Upgrade rust-analyzer failed, please try again
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:9 (4 by maintainers)
Top Results From Across the Web
User Manual - rust-analyzer
At its core, rust-analyzer is a library for semantic analysis of Rust code as it changes over time. This manual focuses on a...
Read more >rust-analyzer failed to discover workspace in vscode
The rust-analyzer needs a Cargo.toml to detect the workspace. You could create a new rust project with cargo : cargo new your-project.
Read more >Be careful folks! rust-analyzer is currently ... - Reddit
I was able to uninstall rust-analyzer, update all my extensions, and then re-install it. Please let's be kind to both VSCode and Rust, ......
Read more >Set up your dev environment on Windows for Rust
But you could launch a command prompt ( cmd.exe ), and perhaps ... After you've installed VS Code, install the rust-analyzer extension.
Read more >Rust analyzer is not working
If you get a prompt to update the Rust-Analyzer extension when you start VS code accept it. You may also get a prompt...
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
@linde12 this error is properly caused by multiple vim instances.
I’ll try this solution.
I’m on node
v12.16.3
.By the way, I’ve switched to providing the path of the binary with the
rust-analyzer.serverPath
setting and this fixes the issue (though no big surprises here, updates are now delegated to the user).