Vim - Visual bug? - stuck at indexing

[Telmo-Sousa]

Hey everyone,
Today I opened up a project I am working on and I noticed that rust-analyzer was stuck
rust-analyzer ⠇ Indexing 1/6 (core) 16%
For moments I thought it could be a bug on macOS but nothing had changed from last night, I created a new project but still the same so I decided to check for updates but that did not change anything.
I decided to hop-op into my Linux machine and the same thing was happening, even after updating it... very weird, changed to my other distro and same thing was happening... but then I noticed the rust-analyzer was working, even weirder?
Maybe I never noticed this before but was always there...? here is a pic tho :)

[lnicola]

What version do you have?

[Telmo-Sousa]

Sorry I should have posted that yesterday but a long night made me forget that...

~ > rust-analyzer --version

rust-analyzer 1.76.0 (07dca48 2024-02-04)
~ > rustup --version

rustup 1.26.0 (5af9b9484 2023-04-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.76.0 (07dca489a 2024-02-04)`
~ > rustc --version

rustc 1.76.0 (07dca489a 2024-02-04)
~ > cargo --version

cargo 1.76.0 (c84b36747 2024-01-18)

[lnicola]

I suggest trying a binary from GitHub Releases, just in case. There were some recent fixes, but I think your version predates the bugs.

[Telmo-Sousa]

Thanks for the help Inicola, I will do that as soon as I have some spare time.
For now it does not bother me that much as it is "working".

[Telmo-Sousa]

well i got it to work properly one time but its back at indexing and when i run the command coc.nvim is suggesting i get a warning
Failed to run build scripts of some packages
funny enough the same thing happened on both of my devices again:
open a project -> it does his thing -> error -> it works -> reopen the project -> stuck at indexing -> it works anyways

[Telmo-Sousa]

I wanted to give a quick update, it seems like it is a visual bug and when I enter command-line mode ":" it seems like the visual "stuck" bug updates to what rust-analyzer is doing now.

Here is a video showcasing that:
https://streamable.com/xwcof9

In the video I open a Rust file with Vim, it starts indexing, cargo check runs smoothly, I close nerdtree, I enter CL mode and the rust-analyzer status updates, I do that repeatedly until it's status is only rust-analyzer.
It is a visual bug I guess because the same thing is happening "under the hood" if I do not do that.

[lnicola]

Yeah, not sure what to say about that. Keep in mind that coc-rust-analyzer is a fork of the official VS Code extension, so unless you can reproduce the issue with Code or another client, this is probably not the best place to ask about issues.