rust-analyzer: Failing to download new server version
This has been reproducible (for me) for a few months; I’m open to the possibility it might be my environment but I don’t see similar with other extensions.
Steps (tentative):
- RA self updates in VS Code
- Little popup appears in the bottom right saying a new server version is available
- Click download button
- Bar progresses to 1% and then the popup vanishes
- Observe that server version is not updated
Fix/Workaround:
- Uninstall the extension
rm -r ~/.config/Code/User/globalStorage/matklad.rust-analyzer/- Reinstall the extension
Details:
OS: Ubuntu 18.04
VSCode:
Version: 1.46.1
Commit: cd9ea6488829f560dc949a8b2fb789f3cdc05f5d
Date: 2020-06-17T21:13:08.304Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 4.15.0-1081-oem snap
I will add a DevTools/Console log to this next time an update comes around, assuming it recurs.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 19 (10 by maintainers)
Commits related to this issue
- Merge #5229 5229: Improve client logging (use output channel and more log levels) r=matklad a=Veetaha The improvements: * Separate output channel allows viewing the logs belonging to only our exten... — committed to rust-lang/rust-analyzer by bors[bot] 4 years ago
- Merge #5243 5243: Consider EPERM error as other vscode processes using rust-analyzer r=matklad a=Veetaha According to: https://github.com/rust-analyzer/rust-analyzer/issues/5009#issuecomment-6545614... — committed to rust-lang/rust-analyzer by bors[bot] 4 years ago
I have seen it since my last comment in this thread, but not in a couple of months and I upgrade whenever the option is available. At this point unless someone else has a replication I think it’s safe to consider it either solved or at least not recurring.
Yes. Running two vscode instances of which one is a library used by the application and referenced locally with
../libnamemay have contributed. It does lead to other issues like failure to reindex as code changes.I will switch to typing into the vscode terminal
code --add ..\libname\to open both in one instanceYou should not kill
rust-analyzer.exe, vscode restarts it automatically, you should close other vscode windows insteadI am glad it works for you. I’ll try to improve our logging situation to allow us get the logs much cleaner from the users.
@xobs do you have this in
settings.json?If not might I ask you to add
and send us the logs from
About > Toggle Developer Tools > Consolewith all objects expanded?