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

Ordered include windows load children for a parent row the top-K holds only while refilling

Abierto
  • ¿Algo no está bien?
#2,151 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
18/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
data

Línea de trabajo

Start with the includes-work oracle in packages/db/tests/query/includes-work-counter-oracle.test.ts, which pins the three overshoot replays. The change belongs in the demand plane: packages/db/src/query/live/collection-config-builder.ts and the subset demand controller. Done means the replays no longer exceed the work bound, the work-bound exclusion is removed from the generated campaigns, and the readiness and demand oracles still pass.

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

Descripción

Problem

An ordered live query with an index-backed parent window can load child rows for a parent row that its settled window does not show. The parent's ordered loader refills the window within one graph run. Until the refill completes, the top-K briefly holds a row outside the settled window, and the include routes that row. The child source then loads that row's children.

The published rows stay correct. The extra work is the children of one parent row for each such checkpoint.

Traces

The includes-work oracle (packages/db/tests/query/includes-work-counter-oracle.test.ts) pins these traces as replays. Each replay loads one child row more than the bound.

  1. A held row moves out. The parent query has orderBy(rank), offset 1 and limit 1. A step moves the parent row at position 0 past every other rank. The top-K briefly shows the moved row before its loader refills the slot. That row's children load.
  2. A tie at the window edge during preload. Two parent rows have the same rank at the window edge. The loader loads the tie after the first prefix. The window first shows one tied row, then the other row, and both rows load their children.
  3. A window move while the loader refills. A step moves a parent row, and a second step inserts a parent row with a copied rank. Then setWindow moves the window. The top-K briefly shows a row outside the moved window.

Why the published rows stay correct

The graph publishes only after the loader settles. The top-K retracts the transient row in the same graph run, so no subscriber receives it. Only the child demand sees the transient row, because setDemand takes effect when the include's parent keys change.

How the oracle observes it

The harness counts the change batches that the parent Collection delivers to the query. At preload, more batches than the initial load show that the ordered loader acquired more rows. After a step, more batches than the step's own parent write show the same. The generated campaigns skip the work bound at those checkpoints only (about 2.5% of them).

Proposed change

Hold include demand until the ordered loader settles. The include records demand changes during a graph run. When the live query's graph loop has no pending work and its loaders are idle, the include sends one net demand change. If that change loads child rows, the graph loop runs again. A transient parent row then adds and removes its key in the same loop, and the child source does not load it.

This change is in the demand plane (packages/db/src/query/live/collection-config-builder.ts and the subset demand controller). It can change when demand starts within a sync turn. The readiness and demand oracles must show that readiness stays correct.

After this change, remove the overshoot from the replays and the work-bound exclusion from the generated campaigns.

This issue was written by Isaac.

Lenguaje dominante
TypeScript
Estrellas
3.9k
Forks
272
Merge medio
1 d 21 min
PR fusionados (30 d)
241

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.