Pin the rest of requirements.txt so a rebuild can't shift the stack silently

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
fastapi, python

Línea de trabajo

Start by reading requirements.txt and the CI and image build install steps described in the issue; compare how each environment resolves dependencies. Then decide between compatible release pins and a generated lockfile, including how updates will be scheduled. Done means both install paths use a consistent dependency set and there is a maintainable update approach.

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

Descripción

#294 was caused by fastapi being unpinned: the image built for v1.7.0 picked up 0.137.0, which
stopped honouring app.openapi_schema, and the service shipped a valid-but-wrong OpenAPI document
without anything failing. That pin is now fastapi~=0.141.1.

Everything else in requirements.txt is still unpinned and can move the same way under an unrelated
rebuild:

requests
httpx
uvicorn
pyyaml
jsonlines
pytest

httpx is the one that matters most — it is how the API talks to Solr — but any of them can change
between a passing CI run and the image ITRB deploys, since the two install at different times from
the same unpinned list.

Needs a decision on approach rather than a quick edit:

  • Pin everything at compatible-release (~=) versions, as fastapi and the opentelemetry packages
    now are?
  • Or generate a fully-pinned lockfile (pip-compile / uv pip compile) from a loose top-level list,
    which also makes CI and the image install identical sets?
  • Either way, how do the pins get bumped on a schedule so they don't rot into a stack we can't
    upgrade?

Related: the opentelemetry packages are already hard-pinned at 1.27.0 / 0.48b0, which is old
enough to be worth reviewing as part of this.

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.