You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is dedicated to one of the follow-up items in this comment: #370 (comment)
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.
The text was updated successfully, but these errors were encountered:
This issue is dedicated to one of the follow-up items in this comment: #370 (comment)
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:
Actual result
All issues resolving the library and its metadata get a "Could not resolve the library foo@1.2.3" message.
The text was updated successfully, but these errors were encountered: