Server initialization failed.
CoreySchnedl opened this issue · 22 comments
👓 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?
- Install extension
- Restart vscode
- See error [Error - 12:45:07 PM] Server initialization failed.
📚 Any additional context?
No response
Same here. We had to downgrade VSCode to 1.89 and disable auto updates to continue having this great plugin working.
Same problem here.
This has been a problem for a while now 😞 I saw VSCode just released a new update and it is still not working.
Yes, i test every 2 days with VS Code insider (1.92.0-insider) the problem still there
The error also happens inside a devcontainer
I have the same issue as well
Would cucumber/language-service#209 help to address this issue @kieran-ryan ?
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
Extensions installed on WSL: Ubuntu:
cucumberopen.cucumber-official@1.10.0
formulahendry.dotnet-test-explorer@0.7.8
ms-azuretools.vscode-docker@1.29.2
ms-dotnettools.csharp@2.39.29
ms-dotnettools.vscode-dotnet-runtime@2.1.1
redhat.java@1.33.0
visualstudioexptteam.intellicode-api-usage-examples@0.2.8
visualstudioexptteam.vscodeintellicode@1.3.1
vscjava.vscode-gradle@3.16.4
vscjava.vscode-java-debug@0.58.0
vscjava.vscode-java-dependency@0.24.0
vscjava.vscode-java-pack@0.29.0
vscjava.vscode-java-test@0.42.0
vscjava.vscode-maven@0.44.0
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?
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
Just had the vscode v1.93.0 update, and same issue.... 😭 😭 😭
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
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