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
Getting error detecting node runtime #1283
Comments
When that stuck terminal appears, does it close if you enter the following command at its prompt?
If it does, please repeat the test but this time enter:
|
@gjsjohnmurray In both cases the terminal closes and the process continues as I described, as if I had closed the terminal by clicking on the trash icon. |
I notice that it seems that scripts are NOT running. These are the logs:
After closing the terminal, it was still not working, so it asked again to install, this time I inspected the environment: Then, after closing the terminal, everything worked. I don't know why that command is failing. |
Ok, I investigated it a little further. The weird thing about this detail is the the extension works fine without the file. After I close the terminal it works just fine and I can open sqlite databases. |
Describe the bug
I have read through the issues and can't find an answer. I don't know what is happening, but I'm getting the message:
Every time code opens.
Logs for sqltools show:
This takes about 5 seconds. The terminal shows:
It seems that the script to set the path at/home/user/.local/share/vscode-sqltools/.node-runtime
worked, the file is written with the path to node.After furter investigating, the file was already there. It is not being recreated. See comment: #1283 (comment)
When I close the terminal the extension then works. I get a notification:
Logs also show it:
(log continues after this)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error.
Screenshots
N/A
Desktop (please complete the following information):
0.5.0
Additional context
It seems to me that the problem is with the terminal, that is not closing.
When using the extension on Windows (same computer, same vscode, as this problem is in WSL) it works.
The text was updated successfully, but these errors were encountered: