Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Restore Query DB receiving histories omitted during PR integration

Offen
  • Stimmt etwas nicht?
#2,188 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
8/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Tech-Stack
sql, sqlite, typescript
Bereich
testing-qa

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
3.9k
Forks
272
Ø Merge
22 Std. 54 Min.
Gemergte PRs (30 T.)
236

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus TanStack/db

Alle Issues in TanStack/db

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.