vscode-powershell: Auto-completion fails due to performance issues

This version is significantly better than before and have not needed to restart in the last 60+ minutes, which was unheard of with the current preview. I’ve been reworking the script I did yesterday which it would freeze on pretty regularly so things have definitely improved.

@TylerLeonhardt I’ve spend about 90 minutes typing functions (for testing I just duplicated existing functions into a dummy project) and auto-complete has worked perfectly so far. Good performance, with no crashes.

I will close this as we close issues when the fix is merged in and this has been merged in.

Awesome - this will be live in… about 10 or so minutes as the PowerShell Preview extension and then if it goes well, Stable will follow next week.

@TylerLeonhardt I’ve created a new issue: [Preview-2020.3.2] Enable Legacy Code Lens not working

Also, it looks like I will be able use 2020.3.2 and just ignore the warning. Won’t know until I give it a go. Tried on another project and it wouldn’t run the Pester tests. It just gave the warning:

Importing Pester module...
WARNING: Failed to import Pester version 5.0.0. You must install Pester module to run or 
debug Pester tests.       
WARNING: You can install Pester by executing: Install-Module Pester -MinimumVersion 5.0.0 
-Scope CurrentUser -Force

UPDATE: The tests will run if I manually import Pester (4.10.1) first.

@TylerLeonhardt I’ve done a brief test with v2020.3.2-preview. In this test intellisense was back to full speed! However, I would not be able to use this version full-time due to the dependency on Pester v5-beta. The ability to run single tests is excellent. Unfortunately it’s not yet stable enough, and I’m getting tests which fail, that don’t fail with Pester 4.10.1. Also, what looks like debug output. I’ll create an issue in the Pester repository.

I’ll try to do a longer test. After which I’ill need to revert to v2020.3.0 with it’s slow intellisense, but working Pester (I unit test most code). Is there a (simple) way to use Pester 4.10.1 with v2020.3.2-preview?

This issue has regressed for me with the latest preview release 2020.3.1. auto-complete doesn’t work at all anymore. Reverting the extension to 2020.3.0 has it working again.

Probably best to track in #2590 which i’ve just found.

@SeeminglyScience

> Import-Module PackageManagement -PassThru


ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Script     1.4.6                 PackageManagement                   {Find-Package, Find-PackageProvider, Get-…

I notice that, since changing the PSModulePath as you suggested above, a new version (1.3.1) of the PackageManagement module has appeared:

> Get-Module PackageManagement -list



    Directory: C:\program files\powershell\7\Modules

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     1.4.6                 PackageManagement                   Desk      {Find-Package, Get-Package, Get… 

    Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     1.3.1                 PackageManagement                   Desk      {Find-Package, Get-Package, Get… 
Binary     1.0.0.1               PackageManagement                   Desk      {Find-Package, Get-Package, Get…

I’ve got the following in my settings:

"powershell.developer.editorServicesLogLevel": "Diagnostic",
"powershell editor services.trace.server": "Verbose",

I’ll leave the extended logging on until I come across the issue. Then I’ll post the logs here.

@SeeminglyScience Thanks for the suggestion. I’ll give that a go and let you know how I get on.

That said, the slow down in auto-complete has only started recently. The PSModulePath has not changed for some time.

It may be worth considering including PackageManagement with the extension 😕

Hmmm, that’s an idea, although we’d need to import it differently the way the module path works.

That just encourages me to get back to work on PSScriptAnalyzer…

OK, now on PS 7 GA and have PSIC displaying. I had done some experimenting with settings a while back and apparently set showOnStartup to false. Fixed.

It’s probably defaulting to preview. Try switching to PowerShell (x64)