-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Function & Cmdlet Name Tab Completion Broken in the ConfigManager (CMSITE) Provider #20803
Comments
It's probably related to the change I made here: #19489 I don't have any way to test tab completion in that provider though. Can you try to CD into that provider and run this: |
Here's the error details from that:
|
Okay, it's probably failing here: https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/CommandCompletion/CompletionCompleters.cs#L4786 because it's somehow finding 2 items with the same name in a folder/container. |
|
Seems like the SCCM team misunderstood the purpose of the PSPath property in the provider system. The whole idea behind the provider system is that you can refer to objects by a path, similar to what you would do on a filesystem but obviously that can't work if the same path points to 21 different objects. |
Thanks |
I've created the PR here: #20815 if you have the time feel free to download the Windows build that will get created as part of the automatic tests and then confirm that the changes I made actually fixed the issue for you. |
📣 Hey @alexlarner, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 aka.ms/PSRepoFeedback |
Sorry, for the late response, but that didn't seem to fix it. And now when I try to run
I believe I downloaded the right build. I downloaded this. |
Thanks. I've found a premade SCCM lab by MS that I can download and test this on. Will investigate and try to fix it in the near future. |
The repo home page Windows link takes you to a I was able to download and run PR-20913-20231212.03 from the I couldn't get the latest two PowerShell-CI-Windows-daily builds to run as they were blocked from running by our company's Windows security. |
📣 Hey @alexlarner, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
Prerequisites
Steps to reproduce
Summary
7.4.0 seems to have broken cmdlet & function name tab completion for all cmdlet & functions while the location is set to the Config Manager provider (
CMSITE
). This was working just fine in previous versions of PowerShell 7.Scope
CMSITE
provider.Workaround
Reverting back to a previous version of PowerShell, i.e.
7.3.10
, fixes the issue.Background Info
My version of the
ConfigurationManager
module shouldn't matter since reverting back to PowerShell 7.3.10 fixes the issue, but just in case I am using version5.2303.1089.1000
of the module.Setup Code
Expected behavior
Actual behavior
Error details
No response
Environment data
Visuals
No response
The text was updated successfully, but these errors were encountered: