Skip to content

incorrect linting happens frequently recently #5864

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
0x8f701 opened this issue Aug 25, 2020 · 8 comments
Closed

incorrect linting happens frequently recently #5864

0x8f701 opened this issue Aug 25, 2020 · 8 comments
Labels
S-unactionable Issue requires feedback, design decisions or is blocked on other work

Comments

@0x8f701
Copy link

0x8f701 commented Aug 25, 2020

First I need to claim that I had never this issue two weeks ago, recently I always see some lint errors, sometimes it's even warning that half of the code in current file is incorrect.

I then exit and open the file again, errors disappear.

For example, the following lint:

image

is suggesting:

image

Environments

  1. coc-rust-analyzer 0.7.15
  2. nvim 0.4.4
  3. rust-analyzer ef9cea9
@0x8f701
Copy link
Author

0x8f701 commented Aug 25, 2020

If I exit and re-open, the errors gone.

@0x8f701
Copy link
Author

0x8f701 commented Aug 25, 2020

image

If I exit and re-open, the errors gone

@flodiebold
Copy link
Member

This looks like the client getting out of sync with the server. This might be a problem with the client, since I don't think we have any reports of this with VSCode. If you can reproduce this in a simple case (like with a file from scratch), can you record a log of the LSP messages?

@0x8f701
Copy link
Author

0x8f701 commented Aug 26, 2020

@flodiebold Hi, I'll try to reproduce it on vscode

Just got another strange thing:

image

@lnicola
Copy link
Member

lnicola commented Oct 15, 2020

Does this still happen?

@lnicola lnicola added the S-unactionable Issue requires feedback, design decisions or is blocked on other work label Oct 15, 2020
@0x8f701
Copy link
Author

0x8f701 commented Oct 15, 2020

Hi @lnicola I confirm that it has been much better now. I kept upgrading to latest rust-analyzer. I'll need some time to confirm it's resolved by testing for a few days.

@lnicola
Copy link
Member

lnicola commented Oct 24, 2020

Ping @GopherJ

@0x8f701
Copy link
Author

0x8f701 commented Oct 24, 2020

@lnicola Hi, since I'm not able to reproduce it using latest RA, I'll close it, thanks for all of your support and notification!

@0x8f701 0x8f701 closed this as completed Oct 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-unactionable Issue requires feedback, design decisions or is blocked on other work
Projects
None yet
Development

No branches or pull requests

3 participants