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

Server initialization failed. #234

Open
CoreySchnedl opened this issue Jun 11, 2024 · 16 comments
Open

Server initialization failed. #234

CoreySchnedl opened this issue Jun 11, 2024 · 16 comments
Labels
🐛 bug Defect / Bug

Comments

@CoreySchnedl
Copy link

👓 What did you see?

[Error - 12:45:07 PM] Server initialization failed.
Message: Request initialize failed with message: bad export type for tree_sitter_c_sharp_external_scanner_create: undefined
Code: -32603
[Error - 12:45:07 PM] Cucumber Language Server client: couldn't create connection to server.
Message: Request initialize failed with message: bad export type for tree_sitter_c_sharp_external_scanner_create: undefined
Code: -32603

Using cucumber v1.10.0
Using vscode in WSL v1.90.0

✅ What did you expect to see?

The extension working. It is currently not usable.

📦 Which tool/library version are you using?

Using cucumber v1.10.0
Using vscode in WSL v1.90.0

🔬 How could we reproduce it?

  1. Install extension
  2. Restart vscode
  3. See error [Error - 12:45:07 PM] Server initialization failed.

📚 Any additional context?

No response

@kieran-ryan kieran-ryan added the 🐛 bug Defect / Bug label Jun 11, 2024
@dcuenca-fluidra
Copy link

Same here. We had to downgrade VSCode to 1.89 and disable auto updates to continue having this great plugin working.

@jm-paulin
Copy link

Ah, just saw that. created #235. will close as this is a dup.

@jclery-pass
Copy link

Same problem here.

@barrymichaeldoyle
Copy link

This has been a problem for a while now 😞 I saw VSCode just released a new update and it is still not working.

@elDin-Dev
Copy link

Yes, i test every 2 days with VS Code insider (1.92.0-insider) the problem still there

@kieran-ryan kieran-ryan pinned this issue Jul 4, 2024
@jhassine
Copy link

jhassine commented Jul 18, 2024

The error also happens inside a devcontainer

@martin-shields-sage
Copy link

I have the same issue as well

@jm-paulin
Copy link

Would cucumber/language-service#209 help to address this issue @kieran-ryan ?

@rolger
Copy link

rolger commented Aug 14, 2024

It also fails for me with the same message. Maybe this could help:

I setup an enviroment in gitpod and the same error occured. Then I tried the same on my Window 10 environment and it worked fine. So, really was wondering what is the difference. Then I used a local installation of Ubuntu and it fails again. So it seems that it depends on the operating system.

Version: 1.92.1 (system setup)
Commit: eaa41d57266683296de7d118f574d0c2652e1fc4
Date: 2024-08-07T20:16:39.455Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

and

@guenhter
Copy link

I also get this problem. What is the right location to address this issue: Is it the cucumber-language-server, it is tree-sitter? I guess it is not the vscode cucumber plugin itself, is it?

@Ramin2c
Copy link

Ramin2c commented Sep 5, 2024

I just tested and the issue is still there in 1.90.0, 1.91.0 and 1.92.0
Downgraded to 1.89.0 and it works like it should.

Used winget to install an older version:

winget install -e --id Microsoft.VisualStudioCode -v 1.89.0

NOTE: the current version needs to uninstalled, either manually or through Programs

@jm-paulin
Copy link

Just had the vscode v1.93.0 update, and same issue.... 😭 😭 😭

@ViniciusResende
Copy link

Facing the same issue with the following:
WSL
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.4169

Visual Studio
Version: 1.93.1 (user setup)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

Linux
Distributor ID: Ubuntu
Description: Ubuntu 22.04.4 LTS
Release: 22.04
Codename: jammy

@naadev
Copy link

naadev commented Oct 4, 2024

Same here:

Version: 1.94.0 (user setup)
Commit: d78a74bcdfad14d5d3b1b782f87255d802b57511
Date: 2024-10-02T13:08:12.626Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.19045

Cucumber VSIX
v1.10.0

@romainwg
Copy link

Same here:

WSL:

WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.2314
Node version: v21.6.2

Visual Studio Code:

1.95.3
f1a4fb101478ce6ec82fe9627c43efbf9e98c813
x64

Installed Extensions:

[email protected]

Linux:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.5 LTS
Release: 22.04
Codename: jammy

@mhvelplund
Copy link

Still broken in:

Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

... on a related note: it's bad enough I have to write unit tests in the 🫏backwards format, but when the plugin that makes it bearable stops working ... I'm not ashamed to say I had a little cry :)

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

No branches or pull requests