microsoft / microsoft/winget-cli

DSC error that tells you to check log should suggest where LOG is

Open
#4,370 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Output Command-Configure Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Brief description of your issue

I created .winget file pointing to private store app. This will fail the Store access from winget, because i need to log in to the store.

Error:
Apply :: WinGetPackage
The configuration unit failed while attempting to test the current system state.
An error occurred while searching for packages: CatalogError

My issues:

  1. CatalogError: This is pretty cryptic. Why not just say we cannot access the Source if that is the issue.
  2. ""
    Why make me do extra work when winget can tell me:
    OPTIONS
    A)
    See C:\Users\WDAGUtilityAccount\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\WinGet-2024-04-11-09-03-54.698.log
    for additional details.

B) suggest, Re-Run the command with the --Logs and --verbose-logs for additional details.

C) Simply tell the user what is wrong so they do not need to look at the log.

image

Steps to reproduce

In SandBox, run the following .winget once you have updated the id to be canary build of a store app that requires permission

properties:
configurationVersion: 0.2.0
resources:

  • directives:
    allowPrerelease: true
    description: private app
    resource: Microsoft.WinGet.DSC/WinGetPackage
    settings:
    id:
    source: msstore
Expected behavior

Better error handling. see suggestions

Actual behavior

image

Environment
C:\Users\WDAGUtilityAccount>winget --info
Windows Package Manager v1.7.10861
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26100.1000
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.22.10861.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin with the Microsoft.WinGet.DSC/WinGetPackage path for an msstore source and reproduce the CatalogError using the provided sandbox configuration. Compare the current log-message behavior with the --Logs and --verbose-logs options; done means the failure explains the source or access problem and provides a usable log location or command.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.