Starting client failed

wiechecprzemyslaw

After latest update I'm getting:
[Error - 19:41:52] Starting client failed
Launching server using command /home/piniol/.vscode/extensions/devsense.phptools-vscode-1.3.6609/out/server/Devsense.PHP.LanguageServer failed.

Ubuntu 20.04

wiechecprzemyslaw

Looking at previous version directory (/home/piniol/.vscode/extensions/devsense.phptools-vscode-1.2.6549/out/server) I can see that it contains "Devsense.PHP.LanguageServer.pdb" file which is missing in "devsense.phptools-vscode-1.3.6609/out/server". I can't tell that this is the problem...

Arkadiy

I'm facing the same issue. Ubuntu 20.04 on WSL 2. I reverted the extension to the previous version until it gets fixed.

AdrienRuiz

Hello, same issue here, can't use the extension.

NateSwanson

Same issue here, the clearly wasn't tested on Ubuntu 20.04.

wiechecprzemyslaw

Teted on second computer, it looks like installation hangs:

PHP Tools extension started.
Found PHP, version: 7.2.34-21, Xdebug: not loaded.
Info: 'dotnet' runtime is missing.
Downloading PHP Tools dependencies (linux-x64-1.3.6609) ...
URL: https://devsenseblob.azureedge.net/phptools/vscode/linux-x64-1.3.6609.zip
Downloading (26928kB):
......................Download Successful.
Installing package 'linux-x64-1.3.6609'

JakubMisek

Thank you all for reporting the issue. We'll try to fix it within today (still not sure what's causing it).

~~For the Starting client failed error, may I ask to try the following command:~~
~~dotnet --list-runtimes~~

Edit: for those who are interested - seems one of the packages changed to have an asynchronous API instead of using callbacks. We haven't tested this particular case. Working on it. Sorry for troubles.

JakubMisek

quick fix for now is calling

chmod +x Devsense.PHP.LanguageServer

in the out/server directory

JakubMisek

we have released the fix - v1.3.6616

thank you all for letting us know

wiechecprzemyslaw

Seems ok, had to disable and reenabe the extesion to start working.

JakubMisek

Yes, VSCode needs you to restart the extension before the update gets activated. Although there should be a button for that, or you can restart VSCode itself.

Thank you for confirming.