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

Cloud Code YAML Support: Server initialization failed. #862

Open
ivan-toriya opened this issue Nov 3, 2023 · 3 comments
Open

Cloud Code YAML Support: Server initialization failed. #862

ivan-toriya opened this issue Nov 3, 2023 · 3 comments
Assignees
Labels
area/yaml language server kind/bug Something isn't working priority/p2 Needs action later

Comments

@ivan-toriya
Copy link

ivan-toriya commented Nov 3, 2023

Version information

Cloud Code Extension version: v2.1.1

VSCode:
Version 1.84.0
Commit: d037ac076cee195194f93ce6fe2bdfe2969cc82d
Date: 2023-11-01T11:28:21.782Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0

OS: Linux x64 6.2.0-36-generic

Cloud SDK: 453.0.0

Description:
Every time I start VSCode there are errors in Cloud Code YAML Support output:

[Error - 4:53:14 PM] Server initialization failed.
  Message: Request initialize failed with message: EISDIR: illegal operation on a directory, read
  Code: -32603 
[Error - 4:53:14 PM] Cloud Code Yaml Support client: couldn't create connection to server.
  Message: Request initialize failed with message: EISDIR: illegal operation on a directory, read
  Code: -32603 

Repro step:
Not sure. For me it always appears when I start VSCode with Cloud Code extension.

@j-windsor j-windsor added kind/bug Something isn't working priority/p2 Needs action later area/yaml language server labels Nov 6, 2023
@nicni16
Copy link

nicni16 commented Jan 8, 2024

I have the same error.

@jeremybramwell
Copy link

image
I have these three error messages opening every few minutes all day long.

I use VSCode with a WSL Remote backend on windows 11.

@ttosta-google
Copy link
Collaborator

The fix will be available in the upcoming release 2.17.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/yaml language server kind/bug Something isn't working priority/p2 Needs action later
Projects
None yet
Development

No branches or pull requests

6 participants