Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

upgrade --from v1 leaves contradictory infra state: v1 per-plugin docker-compose DBs and .env.test targets that don't exist

Abierto
  • ¿Algo no está bien?
#651 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
docker-compose, postgresql, typescript
Área
database, devops

Línea de trabajo

Start by tracing the bos upgrade --from v1 flow and its audit logic, then inspect the generated docker-compose.yml and .env.test handling. Compare the resulting child project configuration with the platform repository’s four service setup described in the issue. Done means stale per-workspace services and invalid test database targets are either updated to the v2 shape or reported clearly by the audit.

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

Descripción

Found during the nearbuilders.org v2 upgrade (NEARBuilders/nearbuilders.org#305).

What

After the managed upgrade, the child repo is left with:

  • docker-compose.yml still describing the v1 topology — one postgres container per workspace (11 services with their own ports/volumes in nearbuilders.org), while the v2 code model is one shared postgres with plugin_<slug> schema scoping and ephemeral PGlite dev defaults. Root dev:postgres* scripts still point at the stale file.
  • .env.test pointing at services that don't exist — nearbuilders.org's copy referenced api_test_db/auth_test_db on ports 5434/5435, which under the v1 compose file were activity_db/builders_db. Any test loading it hits the wrong database or fails.

Why

The upgrade reconciles code/config but not infra files. The v2 topology shift (DB consolidation, ADR 0033) is exactly the kind of change that makes leftover infra files silently wrong.

Suggested fix

During bos upgrade --from v1 (or the audit): detect a generated per-workspace compose topology / .env.test targets that reference nonexistent services, and either regenerate them in the v2 shape (shared postgres + plugin_<slug> schemas + *-test services, mirroring the platform repo's own docker-compose.yml) or add explicit audit warnings listing the stale services.

Reference shape: the platform repo's own docker-compose.yml (4 services: api, auth, api-test, auth-test) is the pattern children should end on.

Lenguaje dominante
TypeScript
Estrellas
5
Forks
3
Merge medio
9 h 48 min
PR fusionados (30 d)
152

Preparar el entorno

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 NEARBuilders/everything-dev

Todos los issues de NEARBuilders/everything-dev

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.