Coordinator: adapter.configuration hides which binding, reference and rule failed
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in crates/registry-coordinator/src/adapters.rs at config_error() and list its 24 call sites, grouping them by which of the five causes each one represents. Follow the secret-reference path (resolve, read as UTF-8, parse the JWK, build the endpoint) to see which binding name and runtime-file key are in scope at each site, and read the wording used in #1433 and #977. Done looks like one message per failure naming the binding, the key such as authorization.signingKeyRef, and a value-free cause, with a test per cause and no secret bytes printed.
由索引模型根据 Issue 内容生成。
描述
Problem
When a product binding cannot be built, Coordinator reports one message whatever the cause: adapter.configuration: product binding or secret-file configuration is invalid. It names neither the binding, the reference, nor the rule that failed.
Observed during the Stage 0 adopter run for #2745. coordinator serve on an example runtime file failed with that message. The cause was a missing private JWK file named by authorization.signingKeyRef. Finding it meant reading the runtime file against the secret root by hand.
Where it collapses
crates/registry-coordinator/src/adapters.rs defines config_error() and calls it from 24 sites with .map_err(|_| config_error()). These include:
- resolving the secret reference;
- reading it as UTF-8;
- parsing the private JWK;
- building the endpoint.
Proposal
Keep the adapter.configuration code. Make the message name:
- the connection or binding name;
- the runtime-file key, such as
authorization.signingKeyRef; - one value-free cause, from a small closed set: missing file, refused file (mode, ownership or link), not UTF-8, not a valid private JWK, or invalid endpoint.
Never print the secret bytes. Casework and BReg do the same through #1433 and #977, so reuse their wording.
Add a test per cause.
- 主要语言
- Rust
- 星标
- 2
- 派生
- 0
- 平均合并
- 9 小时 48 分钟
- 30 天内合并 PR
- 151
环境准备
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
registrystack/registry-stack 的其他 Issue
-
area:breg enhancement
难度 2/5 1-3 小时 新手友好度 65/100
registrystack/registry-stack#2765 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
registrystack/registry-stack#2761 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
registrystack/registry-stack#2743 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
registrystack/registry-stack#2706 ·
维护者通常 1 天内回复
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directory未关闭
难度 2/5 1-3 小时 新手友好度 83/100
registrystack/registry-stack#2704 ·
维护者通常 1 天内回复
查看 registrystack/registry-stack 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
难度 1/5 1 小时以内 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 1/5 1 小时以内 新手友好度 82/100
stackabletech/airflow-operator#898 ·
维护者通常 1 天内回复
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)可能已有人在做 @zyl71 今天认领。 未关闭
难度 1/5 1 小时以内 新手友好度 88/100