Skip to content
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

Editor stuck in out of sync state, all services are broken #11385

Closed
Peter-Juhasz opened this issue Jan 13, 2025 · 5 comments · Fixed by #11665
Closed

Editor stuck in out of sync state, all services are broken #11385

Peter-Juhasz opened this issue Jan 13, 2025 · 5 comments · Fixed by #11665

Comments

@Peter-Juhasz
Copy link

VS 17.13 P2.1

Potentially a new occurrence of #10759, at least the symptoms are the same, but don't know how to reproduce.

Image

20250113-2050-11.5206610.mp4

This is the only log I got:

[LSP][LanguageServer.Semantic.LSPCSharpSemanticTokensProvider] [21:45:27.3641380] We are behind the C# version which is surprising. Could be an old request that wasn't cancelled, but if not, expect most future requests to fail. We were wanting 251 but C# is at 254.

Reopening the file resets and solves the issue.

@Peter-Juhasz
Copy link
Author

Image

@Peter-Juhasz
Copy link
Author

I still get this from time to time, this is today with VS 17.14 P2:

Image

Image

@Peter-Juhasz
Copy link
Author

Finally, here is a repro:

As soon as I commit the completion Name it is game over.

20250325-1037-13.5825862.mp4

It works if I type like super slowly, but if I type with normal speed, it messes up everything.

@davidwengier
Copy link
Member

davidwengier commented Mar 27, 2025

Thanks @Peter-Juhasz!!! I can repro this, and in fact for me it happens just before I commit the completion, just while typing the property name, as completion pops up. Timing is crucial though, and it is a little tricky, but its a start to investigate at least.

@davidwengier
Copy link
Member

Well, you called it out in your original post, and I should have paid more attention to it: This is also caused by provisional completion. I think, somewhat hilariously, that we've actually made things faster enough that we're now hitting good enough timing to surface these bugs 🤦‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants