rust-analyzer.upgrade gives "Error: ETXTBSY: text file is busy on"
See original GitHub issueWith a rust file open and trying to upgrade to last release I get on :CocCommand rust-analyzer.upgrade
:
[coc.nvim] error: Uncaught exception: Error: ETXTBSY: text file is busy, open '/home/francisco/.config/coc/extensions/coc-rust-analyzer-data/ra_lsp_server'
Then the downloading status keep spinning and doesn’t go away.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
"ETXTBSY text file is busy" preventing extension from working
rust -analyzer/rust-analyzer-linux binary a few days ago, and it is still running on my computer (probably a different bug). Now, the prompt " ......
Read more >error "ETXTBSY: text file is busy" on npm install - Stack Overflow
I ran into the same thing on Windows 10 + VirtualBox (VBox) + Vagrant + Laravel Homestead when I wanted to change to...
Read more >Error ETXTBSY text file is busy on npm install - Edureka
When running npm install [any package] or even npm install on homestead I get the following error: npm ERR ... it doesn't exist....
Read more >Upgrade fails due to "text file busy" - Ubuntu - Launchpad Bugs
I cannot upgrade to the current impish, getting the following error (even in a root shell in recovery mode): $ sudo apt --fix-broken...
Read more >neoclide/coc.nvim - Gitter
[coc.nvim] Command error: Error: ETXTBSY: text file is busy, open '/home/francisco/.config/coc/extensions/coc-python-data/languageServer.0.3.38/Microsoft.
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
This is still happening for me for quite a while again and I’ve been silently ignoring and restarting neovim. Always happening after auto updates.
@fannheyward nice, I tried, it works. But just a warning, it works if you have just one [neo]vim instance open. While I was trying to update I got the same error, and noticed that I had another rust-analyzer process running, which was due to a neovim instance I forgot open in a tmux pane.