-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Comments
If I exit and re-open, the errors gone. |
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? |
@flodiebold Hi, I'll try to reproduce it on vscode Just got another strange thing: |
Does this still happen? |
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. |
Ping @GopherJ |
@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! |
Uh oh!
There was an error while loading. Please reload this page.
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:
is suggesting:
Environments
The text was updated successfully, but these errors were encountered: