microsoft / microsoft/winget-cli
Improve error messaging for unavailable source/cache
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 26.4k
- Forks
- 1.8k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 15
Description
Experiencing this issue now. Found the root cause to be that https://winget.azureedge.net/cache/source.msix is returning a 404 error. A 404 error should be communicated to the user in a more direct way than a generic "data is missing" message.
Edit - additional info:
Windows Package Manager v1.1.13405
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.22000.348
Package: Microsoft.DesktopAppInstaller v1.16.13405.0
Edit 2 - https://winget.azureedge.net/cache/source.msix is no longer returning a 404 error, and winget functionality is restored on my system. Probably a temporary issue server-side. Should still be better communicated to the end user.
Originally posted by @NPittinger in https://github.com/microsoft/winget-cli/issues/1348#issuecomment-994115973
Contributor guide
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 examining the WinGet CLI handling for the source.msix cache URL, using the reported 404 at https://winget.azureedge.net/cache/source.msix as the failure case. The work is done when an unavailable source produces a direct, user-facing error instead of the generic "data is missing" message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100