(Preview) PowerShell Command Explorer completely empty (Logs included)

[mkanet]

• Slack Community Chat: https://powershell.slack.com (you can sign-up at http://slack.poshcode.org/ for an invite)
• Gitter Chat: https://gitter.im/PowerShell/vscode-powershell

The Sidebar PowerShell Command Explorer doesn't have anything listed there.

• I am using the latest version of the PowerShell Extension for VSCode.
• I'm using Windows 10 (Version 2004) with native PowerShell 5.1.

Below, are the respective diagnostic logs when I navigate to the PowerShell Command Explorer:

Logs: EditorServices.log StartEditorServices.log vscode-powershell.log

Thank you for your time and hard work.

[rjmholt]

I'm able to reproduce this locally, at first. After waiting a bit the explorer populated. In your case, does the command explorer simply never populate or do entries appear after a while?

[mkanet]

@rjmholt Thank you for your reply. I tried waiting several minutes... nothing happens, unfortunately.

It used to populate after only 5 seconds when it used to work on the same machine. Now, it doesn't populate at all. I'm not sure what else to try other than posting the debug logs above.

[SydneyhSmith]

Thanks, looks like this will need some deeper investigation

... fyi: @corbob

[corbob]

🤔 I believe I've seen instances where the sidebar doesn't load initially, and you must hit the refresh button to get it to load. Not sure if that's related to https://github.com/PowerShell/vscode-powershell/issues/2949 or like this issue (or if they're both related). I'll try to take another look at both this week and see if I can repro.

IIRC there was a setting added for not refreshing the first time, I presume that's not at play here though.

[mkanet]

🤔 I believe I've seen instances where the sidebar doesn't load initially, and you must hit the refresh button to get it to load. Not sure if that's related to #2949 or like this issue (or if they're both related). I'll try to take another look at both this week and see if I can repro.

IIRC there was a setting added for not refreshing the first time, I presume that's not at play here though.

@corbob , I really appreciate your effort to look into this issue. In my case, it doesn't make any difference if I manually press the refresh icon or not. The Command Explorer remains empty. This used to work for me a couple of years ago on the same PC. I'm not sure what changed to cause this to stop working. As far as I know, my setup has remained unchanged when it comes to PowerShell. I'm still using the same PowerShell that came with Windows 10:

PSVersion 5.1.19041.610 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.610 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1

If there's any other information you need from me other than the debug logs I've provided, please let me know.

[SydneyhSmith]

Thanks @mkanet can you try running Get-Command in the integrated console and see if that returns anything for you?

[mkanet]

Thanks @mkanet can you try running Get-Command in the integrated console and see if that returns anything for you?

get-command works fine both within the integrated terminal (panel) and outside of VSCode

My apologies if I misunderstood.

[SydneyhSmith]

@mkanet thanks for testing that out, that was exactly what I was asking....we will look into this when we have time...thanks!

[mkanet]

@SydneyhSmith thank you so much for all your hard work!

[ghost]

This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information!

[andyleejordan]

I see that repro info was not actually needed, the label was just never removed. Re-opening!

[allenschei]

Hello, I have exactly the same issue and test results as mkanet with the latest VSCode 1.66.2 using PS 7.2 on Windows 10 19044.1645. Was a solution discovered for this issue?

Thank you!

[andyleejordan]

Hello @allenschei! The latest code is available in the PowerShell Preview for VS Code, and includes a myriad of fixes. Could you verify if this issue still reproduces using the preview extension?

[allenschei]

Hello Andy, thanks for your reply. I installed the PowerShell Preview extension and I’m getting the same result. The preview pane on the left is completely empty.

Also, I just installed VS Code for the first time on Saturday 24th.

Thank you!

Allen Schei IT Systems Crown Enterprises dba: Sportsman and Ski Haus, Tri-State Outfitters

406-260-4800 @.@.>

@.@.

From: Andy Schwartzmeyer @.> Sent: Monday, April 25, 2022 10:17 AM To: PowerShell/vscode-powershell @.> Cc: Allen Schei @.>; Mention @.> Subject: Re: [PowerShell/vscode-powershell] (Preview) PowerShell Command Explorer completely empty (Logs included) (#3101)

Hello @allenscheihttps://scanmail.trustwave.com/?c=22645&d=58nm4iBdRg76sVPYv7jDrYAsBIq4DTT3Q09puKBkNg&s=1240&u=https%3a%2f%2fgithub%2ecom%2fallenschei! The latest code is available in the PowerShell Preview for VS Codehttps://scanmail.trustwave.com/?c=22645&d=58nm4iBdRg76sVPYv7jDrYAsBIq4DTT3Qxpt7fAwPg&s=1240&u=https%3a%2f%2fmarketplace%2evisualstudio%2ecom%2fitems%3fitemName%3dms-vscode%2ePowerShell-Preview, and includes a myriad of fixes. Could you verify if this issue still reproduces using the preview extension?

— Reply to this email directly, view it on GitHubhttps://scanmail.trustwave.com/?c=22645&d=58nm4iBdRg76sVPYv7jDrYAsBIq4DTT3Q0k-76sxOA&s=1240&u=https%3a%2f%2fgithub%2ecom%2fPowerShell%2fvscode-powershell%2fissues%2f3101%23issuecomment-1108776857, or unsubscribehttps://scanmail.trustwave.com/?c=22645&d=58nm4iBdRg76sVPYv7jDrYAsBIq4DTT3Q0hu7_YzOg&s=1240&u=https%3a%2f%2fgithub%2ecom%2fnotifications%2funsubscribe-auth%2fAOYNML2A7ROGUHIDHOQJDUTVG3AONANCNFSM4VAQ7HKQ. You are receiving this because you were mentioned.Message ID: @.@.>>

[malimal99]

any solutions? have the same issue.

[andyleejordan]

Is there any chance either of you have powershell.sideBar.CommandExplorerExcludeFilter set to something?

[malimal99]

It does not look like it. I assume you mean from defaultsettings.json/

// Specify array of Modules to exclude from Command Explorer listing.
"powershell.sideBar.CommandExplorerExcludeFilter": [],

// Specifies the visibility of the Command Explorer in the PowerShell

Side Bar. "powershell.sideBar.CommandExplorerVisibility": true,

[allenschei]

I can't find the defaultsettings.json file, but here it is in Settings

[andyleejordan]

Hey @mkanet, I know this issue is from 2020. Is it still reproducing for you? I'm going to mark as "needs feedback" so it will auto-close in a week if I don't hear back from. For other users posting, if you are having problem today, please file a new issue so we can get back to you. Thanks all!

[mkanet]

@andschwa This feature stopped working for me a long time ago on both of my PCs. I provided all the necessary logs when I opened this issue already. Maybe a new duplicate issue could be opened by someone else if this issue auto-closes. Maybe they would have better luck getting the issue fixed.

[andyleejordan]

Is it still reproducing with the latest version of PowerShell, the extension, and VS Code? They've all gone through a ton of updates in the last three years since this was opened, so I want to confirm the bug is still extant.

I can't do much with the original logs provided from Extension v2020.6.0, as both the server and client have changed quite a ton so the logs no longer correlate. If it repros with v2023.4.1-preview, please get me some fresh logs so I can take a look!

Thanks!!

[mkanet]

Is it still reproducing with the latest version of PowerShell, the extension, and VS Code? They've all gone through a ton of updates in the last three years since this was opened, so I want to confirm the bug is still extant.

Yes, the same issue has been present on all versions of PowerShell extension (both previous and regular version). However, I am still using an older version of VSCode (version: 1.56.2 05/12/2021) due to another unrelated issue. Hence. I'm not in a position to do any more testing. I can close this issue now. If someone else wants to open a new issue with a current version of VSCode, they are welcome to do so.

[andyleejordan]

VSCode (version: 1.56.2 05/12/2021)

Ah, then you'll also be stuck on an older (and broken) version of the extension, v2021.12.0 (or v2022.2.2-preview, if you can get it). That's unfortunate! I hope you're able to get that updated at some point in the future. If you can get v2022.2.2-preview installed, it may be worth trying, as v2021.12.0 does not contain the rewrite of the pipeline that I think ultimately fixed this issue, but that preview does. Thing is, it's a preview while we were in the middle of testing the rewrite so it definitely had other issues.

Thanks for the follow-up, appreciate it!

[ghost]

This issue has been marked as answered and has not had any activity in a day. It has been automatically closed for housekeeping purposes.