Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Improve error message when library metadata request fails

未关闭
#601 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
csharp
领域
tooling

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
C#
星标
486
派生
91
30 天内没有已合并 PR

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

aspnet/LibraryManager 的其他 Issue

查看 aspnet/LibraryManager 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。