-
Notifications
You must be signed in to change notification settings - Fork 32
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
Connection to server got closed. Server will restart. #279
Comments
Yeah, I am using macOS, and I see the same thing happening here with 2.1.1 of the Prisma plugin. I would also note that in the informational page, about the plugin, where it has a link regarding 'Contributing', that the link is dead. It would sure be nice if that was fixed too. ie: Read more about how to contribute to the Prisma VSCode extension |
@janpio, you seem to indicate that this bug needs more information, but, you don't mention what the additional information you need is. So, please mention what you need that has not been provided? |
No additional information required from you, otherwise I would have asked for it. Someone will look into this and figure out if all information is available and if the problem can be reproduced. |
Experiencing this as well. Environment: MacOS Catalina 10.15.5 - 2.9 GHz Quad-Core Intel Core i7 - 16 GB 2133 MHz LPDDR3 Prisma Language Server output:
|
While looking at how to download the previous version of this extension, I note that the 2.1.1 VSIXPackage, when downloaded, is only around 481KB in size. By comparison, the 2.1.0 downloadable is around 25.5MB. |
Getting this as well.
|
I have the same problem.
|
I am also facing same issue |
We are aware and working on a fix right now. @carmenberndt will update here when the release is out. |
We released 2.1.4 that fixed this issue. What happened: We recently restructured this repo to separate the VSCode extension and the language server. The extension was not using the language server npm dependency but instead searched in the corresponding folder in the repo. We now are only accessing the language server through the npm dependency. To ensure that this doesn't happen again, we created the following issue: Please try out 2.1.4 and let us know if there are any issue with it. |
Environment: Windows 10 Pro Build 19645.mn_release.200605-1502 with and without WSL 1
Plugin Version: Prisma 2.1.1
VSCode Version: 1.46.1
Error occurs while visiting
schema.prisma
file.Error log:
It seems like the extension is searching in the wrong folder for the language-server. I also tried the latest Prisma Insider vscode plugin without any success
The text was updated successfully, but these errors were encountered: