-
-
Notifications
You must be signed in to change notification settings - Fork 270
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 is erroring. Header must provide a Content-Length property” errors in VS Code #6744
Comments
Roc version is "roc nightly pre-release, built from commit dd9a6ff on Sat May 11 09:12:29 UTC 2024” VS Code is Version: 1.85.0 |
Hi @snej, |
Issues for improvements: |
That will work without the language server. If you introduce an error in to the code, e.g by changing |
Yes, I entered the path to the language server. If you look closely at the error, it looks as though the language server is echoing some compiler status output (about downloading a package) to the HTTP response stream before the response headers are complete, and only afterwards sends the Content-Length header. Perhaps that output is being redirected to the wrong FD?
|
Hmm, what seems wrong to me is that Can you try updating to the latest vscode (1.89)? That version works on my mac. |
Client roc-lang: connection to server is erroring. Header must provide a Content-Length property. {"downloading \u001b[36mhttps":"//github.com/roc-lang/basic-cli/releases/download/0.10.0/vNe6s9hWzoTZtFmNkvEICPErI9ptji_ySjicO6CkucY.tar.br\u001b[0m\n into /Users/snej/.cache/roc/packages\n\nContent-Length: 38"} Shutting down server.
Client roc-lang: connection to server is erroring. Header must provide a Content-Length property. {"{\"jsonrpc\"":"\"2.0\",\"result\":null,\"id\":1}Content-Length: 38"} Shutting down server.
Client roc-lang: connection to server is erroring. Header must provide a Content-Length property. {"{\"jsonrpc\"":"\"2.0\",\"result\":null,\"id\":2}Content-Length: 157"} Shutting down server.
The text in the editor does have colors, though, so I assume the language server is running now.
The text was updated successfully, but these errors were encountered: