name-resolution-exp serves an OpenAPI document with no info.x-translator block

Abierto
#295 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
fastapi, openapi, python
Área
api

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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, so construct_open_api_schema()'s output is built but never served, and it accounts for the missing contact, termsOfService, tags and servers as 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.

Lenguaje dominante
Python
Estrellas
5
Forks
4
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NCATSTranslator/NameResolution

Todos los issues de NCATSTranslator/NameResolution

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.