name-resolution-exp serves an OpenAPI document with no info.x-translator block
还没有人认领这个 Issue。
评估
调研方向
Read #294, which identifies the cause and covers this same issue; this issue is explicitly left open only for a maintainer to close. No implementation work is needed here.
由索引模型根据 Issue 内容生成。
描述
Duplicate of #294 — filed before I spotted it. #294 covers the same thing and has the cause: FastAPI 0.137.0 stopped honouring assignment to
app.openapi_schema, soconstruct_open_api_schema()'s output is built but never served, and it accounts for the missingcontact,termsOfService,tagsandserversas well. Read #294 instead; this one is left open only for a maintainer to close.
https://name-resolution-exp.apps.renci.org/openapi.json serves what looks like FastAPI's default document rather than NameRes's own. Its info block has only:
{"title": "...", "description": "...", "version": "..."}
with no x-translator. Every Translator service needs that block to be registered in SmartAPI, and the other NameRes deployments have it:
| Deployment | info.x-translator.infores |
|---|---|
| https://name-lookup.transltr.io/openapi.json | infores:sri-name-resolver |
| https://name-lookup.test.transltr.io/openapi.json | infores:sri-name-resolver |
| https://name-lookup.ci.transltr.io/openapi.json | infores:sri-name-resolver |
| https://name-resolution-sri.renci.org/openapi.json | infores:sri-name-resolver |
| https://namelookup-es.ci.transltr.io/webapp/openapi.json | infores:sri-name-resolver |
| https://name-resolution-exp.apps.renci.org/openapi.json | absent |
/status at that host reports nameres_version v1.7.0 and babel_version 2026jul22, so it is a real and current deployment, not something half-started (checked 2026-08-31).
Is this a deployment problem, or is exp expected not to carry x-translator? If exp is deliberately outside SmartAPI registration we can exclude it in our tests; if not, the openapi.yml it should be merging in isn't being picked up.
Found by test_openapi_json in TranslatorSRI/babel-validation, which checks every target for the block.
- 主要语言
- Python
- 星标
- 5
- 派生
- 4
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
NCATSTranslator/NameResolution 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 43/100
-
难度 3/5 1-2 天 新手友好度 66/100
-
难度 5/5 一周以上 新手友好度 25/100
查看 NCATSTranslator/NameResolution 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
huggingface/kernels#1006 ·
维护者通常 1 天内回复
-
precond_kda (new op, #1552) backward kernels hit CUDA illegal memory access on Blackwell under triton 3.3.1, pass under triton 3.7.1可能已有人在做 @YYuJLiu 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
fla-org/flash-linear-attention#1749 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
bridgecrewio/checkov#7804 ·
维护者通常 2 天内回复
-
area:filesystem bug need-triage
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
triage/confirmed
难度 2/5 1-3 小时 新手友好度 78/100
agentscope-ai/agentscope#4068 ·
维护者通常 2 天内回复