-
Notifications
You must be signed in to change notification settings - Fork 13
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
Can't restart refact-lsp in some cases #24
Comments
@hazratisulton are you running the plugin from source or from the package installer? |
@digital-phoenix Installed from marketplace |
@hazratisulton the marketplace version is out of date. You'll have to wait for it to be updated. |
Checked yesterday version https://github.com/smallcloudai/refact-vs-classic/actions/runs/7469728225/artifacts/1158463034 - still have problem. Steps to reproduce: |
@hazratisulton can you include the log files? |
updated previous message |
Tested https://github.com/smallcloudai/refact-vs-classic/actions/runs/7588140824. Problem #24 (comment) is still reproducible. |
Disposed object -- that looks like a bug that shouldn't happen in any case. |
@hazratisulton can you confirm if this only happens as a result of creatng a new project after using completions? Does this happen if you don't create a project? |
If there is no http port that RefactLanguageClient.cs opens, then there's no obvious reason for lsp to fail to start.
This could be the case if it was the port, the same hardcoded port, but there isn't any 🤔 |
Steps to reproduce:
Create new file, for example, .cpp.
Use completion.
Restart IDE.
Create new file
Try to use completion.
Expected result:
Refact plugin works.
Actual result:
Completion doesn't work because process refact-lsp did not complete from the previous launch.
Sometimes another reboot may be necessary to reproduce the problem.
Software versions:
Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.8.4
Refact plugin v 0.0.1
Windows 11 Pro 22H2 22621.2861
Logs:
ActivityLog.zip
The text was updated successfully, but these errors were encountered: