VSCode Trial not Working

GavGrayston

After stringing together various free extensions for vscode that didn't quite do the job, I came across PHP Tools. I removed the free extensions and installed PHP Tools, and signed up for a trial license to see what it's like before buying a full license.
Unfortunately, it doesn't appear to be installed correctly - or is the 30-day trial severely cut down?

For example, the PHPUnit tests do not appear in the test explorer, and even the basic IntelliSense is limited.

The PHP log says the extension has started.

PHP Tools extension started.
Found PHP, version: 8.0.3, Xdebug: 3.0.4.
Info: Requiring additional package on macOS.
PHP language server started.

As well as the PHP language server.

PHP Tools server started.
    Path: /Users/Gav/.vscode/extensions/devsense.phptools-vscode-1.2.6549/out/server/Devsense.PHP.LanguageServer.dll
    PID: 66004
    Processing files: .php; .php5`

JakubMisek

Thank you for trying the tools. The trial license is not limited, and according to the log, it has started correctly.

May I ask how did you open your folder/workspace? Is it a local or a remote folder?

What is the actual IntelliSense you see?

A screenshot would help us to understand the problem in more detail.

GavGrayston

Thanks for the reply.

The workspace is a local folder.
Unfortunately, I don't appear to have the option to attach a screenshot.

I have discovered the yellow light bulb icon that comes up, so that shows something is working.
There's still no test explorer, debugging, and lot of the other features mentioned.

JakubMisek

I have a few ideas about what to check.

Is VSCode updated?
Do you have anything additional in your VSCode's settings.json? In the lower right corner of VSCode, you should see "PHP":
Do you have any error in Help / Toggle Developer Console / Console?
If you type something (for example e) in a .php file within <?php tags, does it show something?
Do you have tooltips over functions/variables/classes?

It should be possible to paste screenshots from your clipboard.

GavGrayston

Yes, VSCode is up to date.
It's PHP in the bottom right, version 8.0.3.
Yes, there are errors in the dev console. (Unfortunately, I still can't paste in screenshots - tried on both Chrome, Firefox, and even Edge).
And yes, I have tooltips show up when I type something and hover over class names :-)

Here are the errors and warnings in the dev console.

electron/js2c/renderer_init.js:61 The vm module of Node.js is deprecated in the renderer process and will be removed.
t._load @ electron/js2c/renderer_init.js:61
console.ts:137 [Extension Host] (node:70511) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.(Use `Code Helper (Renderer) --trace-deprecation ...` to show where the warning was created)
S @ console.ts:137
event.ts:487 [fh1] potential listener LEAK detected, having 175 listeners already. MOST frequent listener (1):
check @ event.ts:487
event.ts:488     at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:58:58523
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:58:61006
    at new Promise (<anonymous>)
    at Object.N [as toPromise] (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:58:60987)
    at _.whenInitialized (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:76:4475)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:76:2720
    at w (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:68:11210)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:76:2710
    at new Promise (<anonymous>)
    at _.requestPromise (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:76:2252)
    at Object.call (file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:76:1941)
    at file:///Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:76:7092
check @ event.ts:488
TMScopeRegistry.ts:45 Overwriting grammar scope name to file mapping for scope source.sql.
Old grammar file: file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/extensions/sql/syntaxes/sql.tmLanguage.json.
New grammar file: file:///Users/Gav/.vscode/extensions/cweijan.vscode-mysql-client2-3.8.1/syntaxes/mysql.tmLanguage.json
register @ TMScopeRegistry.ts:45
console.ts:137 [Extension Host] ApplicationInsights:CorrelationIdManager Array(1)
console.ts:137 [Extension Host] ApplicationInsights:CorrelationIdManager Array(1)
console.ts:137 [Extension Host] ApplicationInsights:Sender Array(1)
console.ts:137 [Extension Host] ApplicationInsights:Sender Array(1)

JakubMisek

Thanks. Seems those warnings are there even with clean VSCode; should not cause problems tho. I expect it'll be fixed within new versions of VSCode itself.

The code completion is not showing anything?

Debug might be "suppressed" if you already had debugging set previously for this project (i.e. you have a .vscode/launch.json file there). Otherwise running "Run" / "Start Debugging" should create a new launch profile with PHP setup.

GavGrayston

Code completion is sort of working, but not as well as expected.
For example, if I'm in a unit test class (Extends TestCase), typing $this->assert I would expect it to come up with autocomplete for assertEquals, assertEmpty, etc. from the base class.

I have the code lens for tests enabled in the settings, but that's not coming up either.

JakubMisek

It definitely should. Although assertEquals is a static function; so the editor is not showing it after $this-> ... but I guess it should, as it is a common scenario.

I'll note it into our to-do list, so static functions will be listed even after ->.

The following works as expected:

self::assertEquals

JakubMisek

code completion of static methods using -> has been enabled in the recent update. Closing the issue.

We'll continue improving the related issue. Please let us know anything else we can implement or improve.