Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Restore Query DB receiving histories omitted during PR integration

Ouverte
  • Quelque chose ne va pas ?
#2,188 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
8/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
sql, sqlite, typescript
Domaine
testing-qa

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
TypeScript
Étoiles
3.9k
Forks
277
Merge moyen
22 h 54 min
PR mergées (30 j)
236

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TanStack/db

Toutes les issues de TanStack/db

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.