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

Add way to restart language server for a specific file #3727

Closed
ThadHouse opened this issue Jun 4, 2019 · 5 comments
Closed

Add way to restart language server for a specific file #3727

ThadHouse opened this issue Jun 4, 2019 · 5 comments
Assignees
Labels
Feature Request fixed Check the Milestone for the release in which the fix is or will be available. Language Service

Comments

@ThadHouse
Copy link

#3603 and #2966 are still open, and I still randomly see at least 2966, which seems like a race condition somewhere. Closing the file, waiting for the language server for that file to close, and reopening always solves both issues, so it would be nice if there was a way to manually reset the language server on a file. That way the delay wouldn't be needed, and could just be immediately restarted.

@sean-mcmanus
Copy link
Collaborator

By language server I assume you mean the Microsoft.VSCode.CPP.IntelliSense.Msvc.exe process -- you could trying do some a "kill Microsoft.VSCode.CPP.IntelliSense.Msvc.exe" command.

It sounds like fixing the root bugs might be a better solution. I think they're caused by our didOpen event getting delayed for the custom config provider, but then we receive other messages that aren't delayed.

@ThadHouse
Copy link
Author

I don't want to kill the whole process, I notice in the debug logs that after about 20 seconds it receives a message saying shutting down language server for file *. So I don't know if its just 1 process with multiple files, or 1 process per file, but a way to restart just the server parsing for that file.

Another option would be a button to reforce sending the API data to get intellisense.

I do agree fixing the root bugs would be the best fix, but I know that doing that might take a while.

@bobbrow bobbrow added this to the Backlog milestone Jun 5, 2019
@sean-mcmanus
Copy link
Collaborator

We never output "shutting down language server for file" -- do you mean Shutting down IntelliSense server: <file>? That shutdown terminates the IntelliSense process for the translation unit and not the main extension process. It's one process per translation unit.

@bobbrow
Copy link
Member

bobbrow commented Jun 5, 2019

This would be a relatively easy thing to add.

@Colengms Colengms modified the milestones: Backlog, On Deck Apr 13, 2021
@jureid jureid modified the milestones: On Deck, 1.7.0 Aug 2, 2021
@elahehrashedi elahehrashedi added fixed Check the Milestone for the release in which the fix is or will be available. and removed quick fix labels Sep 21, 2021
@sean-mcmanus sean-mcmanus modified the milestones: 1.7.0, 1.7.0-insiders Sep 23, 2021
@sean-mcmanus
Copy link
Collaborator

The fix is available with https://github.com/microsoft/vscode-cpptools/releases/tag/1.7.0-insiders2 (C/C++: Restart IntelliSense for Active File command).

@github-actions github-actions bot locked and limited conversation to collaborators Nov 30, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature Request fixed Check the Milestone for the release in which the fix is or will be available. Language Service
Projects
None yet
Development

No branches or pull requests

6 participants