Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#651 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
45/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
docker-compose, postgresql, typescript
Ambito
database, devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
TypeScript
Stelle
5
Fork
3
Merge medio
9h 37m
PR unite (30g)
157

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NEARBuilders/everything-dev

Tutte le issue di NEARBuilders/everything-dev

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.