microsoft / microsoft/winget-command-not-found
Suggestion only shown about 50% of the time
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 60
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I'm seeing suggestions show sporadically. This is particularly annoying because I use thefuck, which currently re-runs the command to capture output, which means I usually don't get an autocomplete.
If there's anything I can provide to help troubleshoot this issue, please let me know. Thanks!
Name Value
---- -----
PSVersion 7.4.5
PSEdition Core
GitCommitId 7.4.5
OS Microsoft Windows 10.0.26100
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
get-module Microsoft.WinGet.CommandNotFound
ModuleType Version PreRelease Name ExportedCommands
---------- ------- ---------- ---- ----------------
Manifest 1.0.4.0 Microsoft.WinGet.CommandNotFound
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing intermittent suggestions with Microsoft.WinGet.CommandNotFound 1.0.4.0 on PowerShell 7.4.5 for Windows 10, including commands rerun by thefuck. Trace when command output is captured and compare successful and missing suggestions. Done means identifying the cause and making suggestions appear reliably, with a regression test if the project provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100