vscode-intelephense icon indicating copy to clipboard operation
vscode-intelephense copied to clipboard

v1.10.2 not working with WSL2

Open quotidianvoid opened this issue 1 year ago • 1 comments

Describe the bug None of the Intelephense features work in a Laravel Sail environment using WSL2

To Reproduce Start a new project with Laravel 10 and Sail with Intelephense v1.10.2.

Expected behavior All features work. Reverting back to version 1.10.1 fixes the issue.

Screenshots If applicable, add screenshots to help explain your problem.

Platform and version Windows 10.

quotidianvoid avatar Dec 16 '23 15:12 quotidianvoid

same issue here

zenepay avatar Jan 05 '24 06:01 zenepay

Same issue for me in a Drupal environment with WSL2 and Windows 11. Everything works in version 1.10.1.

technatelogy avatar Mar 20 '24 15:03 technatelogy

Can you post your intelephense settings? Including vscode files.associations and files.exclude.

bmewburn avatar Mar 20 '24 23:03 bmewburn

Here are my file associations:

"files.associations": {
	"*.inc": "php",
	"*.info": "ini",
	"*.install": "php",
	"*.module": "php",
	"*.php": "php",
	"*.test": "php",
	"*.theme": "php",
	"*.tpl.php": "php"
},

Here are the only modified intelephense settings I have:

 "intelephense.files.exclude": [
    "**/.git/**",
    "**/.svn/**",
    "**/.hg/**",
    "**/CVS/**",
    "**/.DS_Store/**",
    "**/node_modules/**",
    "**/bower_components/**",
    "**/vendor/**/{Tests,tests}/**",
    "**/.history/**",
    // "**/vendor/**/vendor/**",
    "frontend/**
],
 "intelephense.environment.phpVersion": "8.1.21",

I'm starting to think it's something more environment specific as I have a different computer (Windows 10, WSL2 same exact intelephense settings) and v1.10.2 is working just fine on it....

technatelogy avatar Mar 21 '24 13:03 technatelogy

I updated the packages in my WSL2 (Ubuntu 20.04) environment and now everything is working on v1.10.2 🤷 so I'm guessing it was just a version issue with something...

technatelogy avatar Mar 21 '24 14:03 technatelogy

apt update fixed this issue for me as well. I’m closing this issue.

quotidianvoid avatar Mar 25 '24 09:03 quotidianvoid