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

Startup does not verify the database schema matches the code

Abierto
  • ¿Algo no está bien?
#352 3 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@titankrypt-gif ya está trabajando en esto.

Desde el 16/10/2026.

  • #463 de @sparkysolutions10-pixel — abierto
  • #537 de @sparkysolutions10-pixel — abierto
  • #553 de @titankrypt-gif — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

area:database difficulty:advanced help wanted points:200 Stellar Wave
Background

prisma/ contains only schema.prisma — there is no migrations/ directory,
so every schema change this project has made has been a prisma db push. That
means there is no record of which schema version is deployed and no check at
startup that the database matches what the code expects.

The failure mode is a process that starts cleanly and then fails on the first
query touching a column that does not exist — at request time, in production,
on one instance of several if a deploy is partial.

What to build
  • A startup check that the schema the code expects is actually present, failing
    fast and naming what is missing.
  • Report schema readiness through /ready (L168) so an instance with a stale
    database never receives traffic.
  • Write down, in docs/, why there are no migrations and what the intended path
    is — adopting Prisma Migrate is a larger decision than this issue, but the
    current state should be a recorded choice rather than an accident.
Acceptance criteria
  • Startup fails fast and names the problem when the database does not match the schema
  • /ready reflects schema readiness
  • The check is cheap enough to run on every boot
  • The absence of a migrations directory is documented with its rationale
  • A test covers the mismatch case

Drips Wave · Complexity: Advanced · 200 points

Repo: Divinity-Labs/Lens. Node + TypeScript, Fastify, Prisma on Postgres,
Redis for queues, Prometheus via prom-client.

Run the tests: npm test. The tests are vitest, not jest. Running jest
against this repo reports "66 suites, 0 tests" and means nothing. A single file
is npx vitest run src/__tests__/yourfile.test.ts.

Load test (prices) is already failing on main and has been for some
time. It is not your PR that broke it. Every other check should be green.

This service prices real assets on Stellar mainnet. A number that is wrong
is worse than a number that is missing, because a caller cannot tell the
difference. Prefer failing loudly over returning a plausible value.

Never elide an address, a contract id or a key in code, a comment or a test
fixture. A previous batch wrote a shortened contract id in an issue text and
five contributors invented plausible-looking ids to fill the gap. Write the
whole thing or do not write it at all.

The house pattern for an outbound deadline already exists — see
src/alerts/delivery.ts, which passes signal: AbortSignal.timeout(10_000) to
fetch. Where an issue below asks for a timeout, copy that, do not invent a
second convention.

Required: Before submitting, join the contributor Telegram so your work can be tracked and counted toward the Stellar Wave: https://t.me/+fxHXq8f1SwlkZDBk

Lenguaje dominante
TypeScript
Estrellas
4
Forks
71
Merge medio
1 d 5 h
PR fusionados (30 d)
59

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 Divinity-Labs/Lens

Todos los issues de Divinity-Labs/Lens

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.