Improve error message when library metadata request fails
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
No file or test is named. Start by tracing the library-resolution path that produces "Could not resolve the library" and compare failures for library names, versions, and metadata requests. Done means the error identifies the failed portion or cause instead of using the same generic message for every failure.
Written by the indexing model from the issue text.
Description
This issue is dedicated to one of the follow-up items in this comment: https://github.com/aspnet/LibraryManager/issues/370#issuecomment-637953775
Functional impact
Error is imprecise about the cause of failure and may lead to user confusion
Minimal repro steps
Happens randomly, no reliable repro
When downloading a library for the first time, if one of the metadata requests fails we get a generic "Could not resolve the library foo@1.2.3".
Expected result
Better indicate the cause of failure or the portion which failed, some ideas:
- Failed to retrieve file metadata for foo@1.2.3
- Failed to retrieve library metadata for foo@1.2.3. Received HTTP response 418.
- Unrecognized library name "foo"
- Unrecognized library version for "foo@1.2.3"
Actual result
All issues resolving the library and its metadata get a "Could not resolve the library foo@1.2.3" message.
- Dominant language
- C#
- Stars
- 486
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
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.
More from aspnet/LibraryManager
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
aspnet/LibraryManager#824 · 1 comment · 3 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
aspnet/LibraryManager#804 · 2 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
aspnet/LibraryManager#829 · 1 comment · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/LibraryManager#820 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
aspnet/LibraryManager#808 · 5 comments ·
All issues in aspnet/LibraryManager
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Type: enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
apache/arrow-adbc#4809 ·
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/vscode-azurefunctions#5197 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
microsoft/microsoft-ui-reactor#1274 ·