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

VS Code Connection to server got closed. Server will not be restarted. #57

Open
swapnil823 opened this issue Mar 6, 2021 · 7 comments

Comments

@swapnil823
Copy link

I am getting following prompt with vscode.

[Info  - 6:11:50 pm] Connection to server got closed. Server will restart.
[Error - 6:11:50 pm] Connection to server got closed. Server will not be restarted.

$ svls --version
svls 0.1.25

svls is in path, I tried launching vs code with the shell that could run svls without any issues.

@dalance
Copy link
Owner

dalance commented Mar 7, 2021

Could you show the stack trace?
I think it will be logged by Help -> Toggle developer tools.

@swapnil823
Copy link
Author

Here is the trace.

workbench.desktop.main.js:731 The SystemVerilog language server server crashed 5 times in the last 3 minutes. The server will not be restarted.
onDidChangeNotification @ workbench.desktop.main.js:731
(anonymous) @ workbench.desktop.main.js:731
fire @ workbench.desktop.main.js:57
addNotification @ workbench.desktop.main.js:733
notify @ workbench.desktop.main.js:1725
(anonymous) @ workbench.desktop.main.js:1680
_showMessage @ workbench.desktop.main.js:1680
$showMessage @ workbench.desktop.main.js:1680
_doInvokeHandler @ workbench.desktop.main.js:1687
_invokeHandler @ workbench.desktop.main.js:1687
_receiveRequest @ workbench.desktop.main.js:1687
_receiveOneMessage @ workbench.desktop.main.js:1687
(anonymous) @ workbench.desktop.main.js:1687
fire @ workbench.desktop.main.js:57
fire @ workbench.desktop.main.js:76
_receiveMessage @ workbench.desktop.main.js:76
(anonymous) @ workbench.desktop.main.js:76
fire @ workbench.desktop.main.js:57
acceptChunk @ workbench.desktop.main.js:76
(anonymous) @ workbench.desktop.main.js:76
I @ workbench.desktop.main.js:2760
emit @ events.js:315
addChunk @ _stream_readable.js:295
readableAddChunk @ _stream_readable.js:271
Readable.push @ _stream_readable.js:212
onStreamRead @ internal/stream_base_commons.js:186

@dalance
Copy link
Owner

dalance commented Mar 8, 2021

Thanks. I can't reproduce this issue yet.
Does this issue happen always? Otherwise the specific source code?
Could you tell me your platform?

@swapnil823
Copy link
Author

swapnil823 commented Mar 16, 2021

Yes, This issue is persistent.
I am using lubuntu.

uname -a
Linux  5.8.0-44-generic #50~20.04.1-Ubuntu SMP Wed Feb 10 21:07:30 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
code --version
1.54.3
svls-code 0.0.1

@ka98
Copy link

ka98 commented Aug 31, 2022

I had the same problem, I installed svls using snap
when I installed it via cargo it worked just fine

@DaveMcEwan
Copy link
Contributor

@ka98 @swapnil823 Have you figured out what your issue was? Or found an acceptable workaround?

@ka98
Copy link

ka98 commented Nov 22, 2022

As I already mentioned I just used cargo to install the package, for some reason snap seems to lack a dependency but I didn't do any further troubleshooting 😄

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

No branches or pull requests

4 participants