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

Restore Query DB receiving histories omitted during PR integration

Abierto
  • ¿Algo no está bien?
#2,188 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
8/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
sql, sqlite, typescript
Área
testing-qa

Línea de trabajo

Start with docs/contributing/oracle-coverage.md near the Query DB ownership section to see which histories are listed as missing, then read load-subset-lifecycle-oracle.test.ts and ownership-lifecycle.oracle.test.ts. Done means new public-history tests with wrong-design controls, scratch failures classified as invalid fixture, production defect or open contract question, and the coverage map updated.

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

Descripción

Coverage gap

The #2134 branch once had public receiving histories for Query Core observer handoff, paused and reentrant replacement fetches, refetch cancellation, and nested fetch order across direct writes. Some did not survive its integration with #2158 at executable merge 2089e0630.

The current merged tree has strong named and generated lifecycle coverage. It does not replay every earlier receiving path. docs/contributing/oracle-coverage.md lists the missing paths near the Query DB ownership section. A scratch merge of the older tests with the published-Core adapter reported 68 failures among 841 tests. Some fixtures assumed an eager signal data descriptor or same-stack physical abort. The current adapter uses a lazy getter and Query Core's release turn. Those fixture failures are not evidence of product bugs; the remaining public-law failures have not been classified.

Oracle owners and acceptance

  • Extend load-subset-lifecycle-oracle.test.ts with outside-observer handoff, cleanup, paused-fetch, and reentrant replacement histories. Compare the physical signal, Query cache, caller settlement, and full public rows after the correct release and application cuts.
  • Extend ownership-lifecycle.oracle.test.ts with nested fetch-start order across accepted direct writes. Add explicit refetch and snapshot histories that compare each caller's result with its own applied replacement.
  • Derive expected outcomes from the Collection sync-adapter contract and Query Collection guide. Do not copy Query DB's current fetch classifier into the reference model.
  • Calibrate at least one wrong-design control at each new public comparison. Classify old scratch failures as invalid fixture, production defect, or unresolved contract question before changing assertions.
  • Update the coverage map with the exercised histories and remaining limits. File confirmed product defects separately. #2176 already tracks non-source Query result provenance.

This is follow-up oracle work. It does not change the bounded identity, primitive SQLite upgrade, or #2158 acquisition claims already reviewed in those PRs.

Lenguaje dominante
TypeScript
Estrellas
3.9k
Forks
277
Merge medio
22 h 54 min
PR fusionados (30 d)
236

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 TanStack/db

Todos los issues de TanStack/db

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.