mirror of
https://github.com/garrytan/gbrain.git
synced 2026-07-27 22:15:33 +00:00
* feat(engine): add deletePages + resolveSlugsByPaths to BrainEngine (v0.41.21.0 T1) Two new REQUIRED methods on the BrainEngine interface, implemented on both Postgres and PGLite engines. Closes the per-file N+1 query pattern that PR #1538 batched on Postgres only. deletePages(slugs: string[], opts: { sourceId: string }): Promise<string[]> — Single SQL round-trip: DELETE FROM pages WHERE slug = ANY($1::text[]) AND source_id = $2 RETURNING slug — Returns slugs ACTUALLY DELETED (D6, codex CDX-8) so callers can filter pagesAffected to exclude phantom slugs (paths in the deletion list but with no DB row). — Single-batch primitive: caller chunks input to DELETE_BATCH_SIZE. Throws if input exceeds the cap. — sourceId is REQUIRED at the type level (D5, codex CDX-10). Asymmetric with single-row deletePage which keeps the optional 'default' fallback for back-compat. v0.42+ TODO to tighten. resolveSlugsByPaths(paths, opts): Promise<Map<path, slug>> — Batch path → slug lookup. Single SQL round-trip: SELECT slug, source_path FROM pages WHERE source_path = ANY($1::text[]) AND source_id = $2 — Missing paths absent from the Map (caller falls back to path-derived slug, same contract as resolveSlugByPathOrSourcePath). — Empty input short-circuits to empty Map (no SQL). src/core/engine-constants.ts (NEW) — Single source of truth for DELETE_BATCH_SIZE = 500. — Both engines import; no engine-from-engine coupling. — Lives outside engine.ts (the interface module) to avoid circular imports. Also updates the deletePage JSDoc (CDX-11): drops the misleading "hard delete is admin-only" framing. `gbrain sync` hard-deletes on every run that sees a deleted file; not admin-only. Co-Authored-By: garrytan-agents <noreply@anthropic.com> Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * perf(sync): batched delete + rename + DRY refactor (v0.41.21.0 T2/T3/T4) Replaces the per-file delete loop (sync.ts:1241-1257) and per-file rename slug-resolve (sync.ts:1263-1295) with interleaved per-batch flows using engine.resolveSlugsByPaths + engine.deletePages. Also refactors resolveSlugByPathOrSourcePath (sync.ts:267) to delegate to the new batch helper when sourceId is set — one owner of the SQL + fallback semantics (D8). ROUND-TRIP COUNTS (73K-delete commit): pre-fix: 73,000 SELECTs + 73,000 DELETEs = 146,000 (~5 hours) post-fix: 146 SELECTs + 146 DELETEs = 292 (~2 minutes) Headline win: a single commit deleting 73K files no longer jams the sync pipeline for hours, no longer cascades staleness across every other source on the brain. Shape (T2 delete loop, per the plan's ASCII diagram): filtered.deleted (73K paths) │ ▼ slice into batches of DELETE_BATCH_SIZE (500) │ ▼ for each batch: abort-check ──► partial('timeout') │ ▼ engine.resolveSlugsByPaths(batch, {sourceId}) ◀── 1 SQL round-trip │ ▼ slugs = batch.map(path => map.get(path) ?? resolveSlugForPath(path)) ◀── pure-JS fallback │ for frontmatter- ▼ fallback slugs try { deleted = engine.deletePages(slugs, opts) ◀── 1 SQL round-trip pagesAffected.push(...deleted) ◀── D6 confirmed only } catch { // D7 decompose: per-slug deletePage, // unrecoverable failures → failedFiles } Per-batch try-catch (D7) decomposes batch DELETE failures to per-slug deletePage so a transient blip on batch 73 doesn't lose 500 deletes — it self-heals to one-at-a-time for that batch only. Unrecoverable per-slug failures land in failedFiles (matching the existing import-loop pattern at sync.ts:~1350). failedFiles declaration hoisted above the delete loop so both delete decompose and import loops feed the same sync-bookmark gate. T4 rename loop: pre-resolves all `from` slugs in batches via resolveSlugsByPaths BEFORE iterating. Per-file updateSlug + importFile calls stay (those are inherently per-file). The try/catch around updateSlug for slug-doesn't-exist preserves verbatim. T3 DRY refactor: resolveSlugByPathOrSourcePath delegates to resolveSlugsByPaths via a single-element array when sourceId is set. When sourceId is undefined (legacy unscoped callers), falls back to the original executeRaw shape — the batch engine surface requires sourceId per D5 (multi-source-bug-class defense). Atomicity coarsening (D3): each batch is one transaction. A mid-batch abort or connection failure rolls back up to DELETE_BATCH_SIZE - 1 successful deletes from the in-flight batch. Sync is idempotent so the next run picks them up via git diff regenerating the deletion list. Documented at the call site + in the deletePages JSDoc. Co-Authored-By: garrytan-agents <noreply@anthropic.com> Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(schema): global page-generation clock + statement-level trigger (v0.41.21.0 T5) Migration v104: page_generation_clock_and_statement_trigger. The pre-v0.41.21.0 query-cache Layer 1 bookmark read MAX(generation) FROM pages to detect "writes happened since cache-store". Two bugs in that contract — independent of any sync work, surfaced by codex outside-voice on the /plan-eng-review pass: 1. The row-level bump_page_generation_trg (migration v91) sets NEW.generation = OLD.generation + 1 on UPDATE. Updating a NON-MAX page didn't advance MAX(generation). Cache silently served stale for any UPDATE-to-non-max page. (CDX-2) 2. The trigger is BEFORE INSERT OR UPDATE — DELETE doesn't fire it at all. Even an AFTER DELETE wouldn't move MAX (surviving rows are untouched). (CDX-1) Fix: single-row page_generation_clock counter, bumped per-statement (FOR EACH STATEMENT — per-row would turn a 73K-row batch DELETE into 73K UPDATEs on the same counter, recreating the bottleneck this PR fixes elsewhere — codex CDX-4). Layer 1 reads the clock value directly (T6, separate commit). Per-row pages.generation stays for Layer 2 (per-page snapshot via jsonb_each + LEFT JOIN pages) which doesn't care about MAX, only per-page advancement. Seeded with COALESCE(MAX(pages.generation), 0) so existing query_cache rows stored under the old MAX semantics aren't all instantly invalidated on upgrade. Their max_generation_at_store stamp compares cleanly against the seeded clock; future writes bump the clock and the bookmark fires correctly. CREATE TABLE page_generation_clock ( id INTEGER PRIMARY KEY CHECK (id = 1), value BIGINT NOT NULL DEFAULT 0 ); CREATE TRIGGER bump_page_generation_clock_trg AFTER INSERT OR UPDATE OR DELETE ON pages FOR EACH STATEMENT EXECUTE FUNCTION bump_page_generation_clock_fn(); Mirror in src/core/pglite-schema.ts so fresh PGLite installs get the table + trigger via SCHEMA_SQL replay. The forward-reference bootstrap probe doesn't need an entry: page_generation_clock is created directly by SCHEMA_SQL (no separate index or FK references it), so the schema-bootstrap-coverage gate is satisfied as-is. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(cache): move Layer 1 to global clock + invalidate empty snapshots (v0.41.21.0 T6) Closes the silent stale-cache bug class that's been live in master since the bookmark feature shipped. Pre-fix, gbrain search would silently serve stale cached results in three independent scenarios: 1. UPDATE to a non-max-generation page (CDX-2) — the row-level trigger advanced per-page generation but didn't move MAX(generation), so the bookmark passed. 2. DELETE of any page (CDX-1) — the trigger didn't fire at all, and even an AFTER DELETE wouldn't move MAX. 3. Empty-result cache row + subsequent matching INSERT (CDX-6 / D20) — page_generations = '{}'::jsonb was "vacuously valid" via Layer 2, surviving any clock bump. Fix: buildPageGenerationsSnapshot (store path) — Replaces the SELECT MAX(generation) FROM pages reads at cache-write time with SELECT value FROM page_generation_clock WHERE id = 1. — Empty pageIds path: only need the clock value (D20 contract). — Combined non-empty path: per-page generation (Layer 2 substrate) + clock value, both folded in one round trip via UNION ALL. CACHE_GATE_WHERE_CLAUSE (lookup path) — Layer 1 reads page_generation_clock.value (single-row O(1) lookup, faster than the pre-fix MAX(generation) backward index scan). — Layer 2 stricter: requires page_generations <> '{}'::jsonb AND the per-page check (not OR with the vacuously-valid `= '{}'` shortcut). Empty snapshots can no longer survive a Layer 1 miss. validateCacheRowAgainstPages (pure validator) — Layer 2 returns false for empty snapshots when Layer 1 fails. — Documented contract change. Backward compat: pre-v0.40.3.0 cache rows have max_generation_at_store = 0 AND page_generations = '{}'::jsonb. On a populated brain, Layer 1 fails (clock > 0). Layer 2 is now stricter so legacy rows invalidate once on first post-upgrade lookup, then the cache fills back correctly. Acceptable one-time miss spike; post-upgrade cache is structurally sound. The clock seed (COALESCE(MAX(pages.generation), 0)) from migration v104 keeps NON-empty legacy rows passing Layer 1 until the next write — they don't all invalidate at once. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * test: cover v0.41.21.0 delete-batch + global clock + cache contract (T7+T8+T9) Tests for every behavior the v0.41.21.0 wave introduces or changes. New test files: test/sync-delete-batch.test.ts (PGLite hermetic) — engine.deletePages: empty input short-circuit, returns confirmed slugs (D6), multi-source isolation, cascade integrity (chunks + links cleared via FK), rejects oversized input. — engine.resolveSlugsByPaths: empty input, present + missing rows, D10 exotic-filename substrate (🌟.md / ทดสอบ.md / عربي.md), source isolation. — D13 pagesAffected filter: 100 deletable + 10 ghost paths → deletePages returns 100 (regression-pin: pre-fix would return all 110 via D6's pre-RETURNING shape). test/sync-delete-batch.slow.test.ts (.slow suffix keeps it out of the fast loop) — 10K-page batched delete completes in <5s on PGLite. Measured 277ms on dev hardware (18x under the gate); pins the headline perf promise. test/sync-rename-batch.test.ts (PGLite hermetic) — 500-rename batch slug-resolve in 1 round-trip (exactly at DELETE_BATCH_SIZE boundary). — Frontmatter-fallback rename: exotic source_paths resolve via the batch SELECT. — Mixed present + missing: partial Map (missing → caller falls back to path-derived). test/page-generation-counter.test.ts (PGLite hermetic) — Statement-level trigger fires once per INSERT statement (raw SQL — NOT putPage, which uses ON CONFLICT DO UPDATE and bumps by 2 in PG semantics). — Statement-level trigger fires once per UPDATE statement. — Headline contract: batch DELETE bumps clock by 1, NOT by row count (25-row batch → +1). — CDX-1 regression: DELETE of non-max page bumps clock. — CDX-2 regression: UPDATE of non-max page bumps clock (raw SQL). — D14 end-to-end: clock advances after batch DELETE → cache rows stamped at the prior clock value are now stale by Layer 1. — CDX-6/D20: empty-result cache + INSERT matching page → clock advances (Layer 1 fires). — Documents the PG quirk: putPage's INSERT...ON CONFLICT DO UPDATE bumps clock by 2 (both INSERT and UPDATE triggers fire). Test-helper update: test/helpers/reset-pglite.ts — Added page_generation_clock to PRESERVE_TABLES so the seeded single-row counter survives resetPgliteState between tests (same treatment as schema_version). Production never truncates. Existing test contract inversions (CDX-6 / D20 fix): test/query-cache-gate.test.ts — Pre-v0.41.21.0 "vacuously valid for legacy empty snapshot" assertion inverted: empty snapshot now invalidates when Layer 1 fires. Add positive CDX-6 regression test (empty-result + INSERT matching page). — SQL shape regression: page_generation_clock in Layer 1 (negative regression guard: MAX(generation) FROM pages MUST be gone). — Empty-snapshot reject guard: `qc.page_generations <> '{}'::jsonb` present; the old `qc.page_generations = '{}'::jsonb OR` shortcut MUST be gone. test/e2e/cache-gate-pglite.test.ts — Pre-v0.41.21.0 "legacy row serves vacuously" test inverted: legacy rows now invalidate on first clock advance post-upgrade. — CDX-1 regression: DELETE bumps clock → cached query for surviving pages invalidates. — CDX-2 regression: UPDATE-to-non-max-page bumps clock → cache invalidates. — CDX-11 comment fix: drop misleading "hard delete is admin-only" framing; gbrain sync hard-deletes on every run. Engine parity extension: test/e2e/engine-parity.test.ts — deletePages parity: same input set, both engines return same string[] of confirmed-deleted slugs (D6). — resolveSlugsByPaths parity: same Map on both engines. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(release): v0.41.21.0 — batched sync deletes + global page-generation clock (T10) VERSION bump (0.41.18.0 → 0.41.21.0; master is at 0.41.20.0 so next free slot per the queue allocator). CHANGELOG entry with the ELI10 lead per CLAUDE.md voice rules. CLAUDE.md annotations on engine.ts, postgres-engine.ts, pglite-engine.ts, sync.ts, and query-cache-gate.ts plus a new entry for engine-constants.ts. llms-full.txt regenerated to match CLAUDE.md (per CLAUDE.md mandatory rule). Co-Authored-By: garrytan-agents <noreply@anthropic.com> Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * dx(test-runner): heartbeat shows real progress instead of 0p 0f Bun's default test reporter doesn't print per-test markers — only a single shard-end summary block when you pass it a file list. The existing heartbeat tried to count `^[[:space:]]+✓` lines as a live pass-count proxy, but bun never emits them in the multi-file mode this runner uses, so every mid-run heartbeat showed `0p 0f` for the entire 12-20 minute wallclock. Users (and agents polling the runner) couldn't distinguish "still bootstrapping" from "wedged" from "almost done." Fix: parse three complementary real-time signals instead. 1. Total files this shard was assigned — parsed from the `[unit-shard N/M] running X files` banner that run-unit-shard.sh echoes before invoking bun test. Available from second 1. 2. PGLite initSchema() count — proxy for "test files started so far." Each PGLite-using test file's beforeAll triggers one initSchema(), which logs `Schema version 1 → 106 (101 migration(s) pending)`. Undercounts because not every test file opens a PGLite engine (covers ~30-60% of files in practice), but it's the only real-time progress signal bun's default reporter leaves in the log. The output uses a `~` prefix to convey "approximate count." 3. Log size in KB — strictly monotonic liveness signal that works even when the PGLite count is still 0 (early-shard startup before the first initSchema fires). 4. Per-shard elapsed time — formatted as MmSSs. New mid-run heartbeat line: [heartbeat] [s1: ~62/190f 476KB 12m31s] [s2: ~63/190f 513KB 12m31s] ... When a shard finishes, the heartbeat upgrades to its final summary including pass/fail counts from bun's end-of-shard summary block: [heartbeat] [s1: done ✓ 2807p 0f] [s2: done ✓ 2784p 0f] ... Portability: BSD awk on macOS doesn't support `match($0, /re/, arr)` with the array sink — that's a gawk extension. The total-files parser uses sed instead so the runner stays portable to the default Mac toolchain. Helpers are pure functions and unit-testable in isolation: pass a log file path, get the parsed number. No mocking. No bun runtime required. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(release): rebump v0.41.23.0 → v0.41.25.0 Per user request — skip v0.41.23.0 / v0.41.24.0 slots to land at v0.41.25.0. Master is at v0.41.22.1, no version-trio collision. Touches VERSION, package.json, CHANGELOG header, CLAUDE.md annotations, src/core/engine-constants.ts header, src/core/migrate.ts migration v106 comment, regenerated llms-full.txt + llms.txt. Migration version (v106) and CDX1-6 trigger semantics unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(schema): reorder migration_impact_log AFTER minion_jobs (CI green) Pre-existing bug in master's SCHEMA_SQL ordering, surfaced by CI on this PR but lived silently on master since v0.41.18.0. migration_impact_log declares `job_id BIGINT REFERENCES minion_jobs(id)`, but its CREATE TABLE was at line 658 while minion_jobs's CREATE TABLE was at line 778. On any fresh-install initSchema() the FK target didn't exist yet: psql:/tmp/schema.sql:672: ERROR: relation "minion_jobs" does not exist postgres-js's `unsafe()` aborts the multi-statement batch on the first error response, so every CREATE TABLE after migration_impact_log (including minion_jobs itself) never ran. Every subsequent CLI subprocess that opened a connection then crashed with `relation "minion_jobs" does not exist` on its first query. Why master CI sometimes passed: the per-shard advisory lock + the test setup's `engine.initSchema()` second pass (which runs the migrations array) would eventually create minion_jobs via the v5 `minion_jobs_table` migration. From there migration_impact_log would land via migration v103 with its FK resolving correctly. But CLI subprocesses spawned by mechanical.test.ts's Parallel Import block open their OWN connections and run a fresh `engine.connect() → initSchema()` — that path runs SCHEMA_SQL FIRST and aborted at the same forward-reference error before the migrations array could repair. Fix: relocate the migration_impact_log CREATE TABLE + its two indexes to AFTER the minion_jobs CREATE TABLE block (lines ~865), keeping the rest of the schema layout intact. PGLite schema (pglite-schema.ts) already had the correct ordering — only Postgres SCHEMA_SQL needed the move. Verified: fresh-DB local repro that previously failed 31/34 tests with `relation minion_jobs does not exist` now passes 78/78 in test/e2e/mechanical.test.ts. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: garrytan-agents <noreply@anthropic.com>
282 lines
11 KiB
TypeScript
282 lines
11 KiB
TypeScript
/**
|
|
* v0.40.3.0 — query-cache-gate.ts (cache invalidation gate)
|
|
*
|
|
* Pure unit tests for the two helpers. Both helpers are pure functions
|
|
* (the validator) or take an engine argument (the snapshot builder); the
|
|
* latter uses a PGLite engine to test the real SQL fragment.
|
|
*
|
|
* Coverage:
|
|
* - buildPageGenerationsSnapshot: empty pageIds, populated pageIds,
|
|
* bookmark capture, missing pages excluded (LEFT JOIN equivalent).
|
|
* - validateCacheRowAgainstPages: vacuously valid for legacy/empty,
|
|
* bookmark short-circuit, single-page bump invalidates, deleted page
|
|
* invalidates, multi-page partial bump invalidates, integer-JSONB
|
|
* shape regression (string-typed values).
|
|
* - CACHE_GATE_WHERE_CLAUSE: source-text shape regression (grep guards).
|
|
*/
|
|
|
|
import { afterAll, beforeAll, beforeEach, describe, expect, test } from 'bun:test';
|
|
import { PGLiteEngine } from '../src/core/pglite-engine.ts';
|
|
import { resetPgliteState } from './helpers/reset-pglite.ts';
|
|
import {
|
|
buildPageGenerationsSnapshot,
|
|
validateCacheRowAgainstPages,
|
|
CACHE_GATE_WHERE_CLAUSE,
|
|
type PageGenerationsSnapshot,
|
|
} from '../src/core/search/query-cache-gate.ts';
|
|
|
|
describe('validateCacheRowAgainstPages (pure validator)', () => {
|
|
test('v0.41.19.0 D20/CDX-6 inversion: empty snapshot invalidates when bookmark fires', () => {
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: {},
|
|
max_generation_at_store: 0,
|
|
};
|
|
// Pre-v0.41.19.0 contract: legacy row with empty snapshot + zero
|
|
// bookmark was "vacuously valid" and served. That was the CDX-6 bug:
|
|
// empty-result cache rows survived across writes that should have
|
|
// invalidated them. Post-v0.41.19.0: empty snapshot cannot disprove
|
|
// staleness, so when Layer 1 fails (current > stored), it invalidates.
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 999, // Clock advanced since store
|
|
page_generations: {},
|
|
});
|
|
expect(ok).toBe(false);
|
|
});
|
|
|
|
test('empty snapshot still serves when bookmark says no writes happened (Layer 1 short-circuit)', () => {
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: {},
|
|
max_generation_at_store: 50,
|
|
};
|
|
// No writes since store → Layer 1 passes → snapshot emptiness doesn't matter.
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 50,
|
|
page_generations: {},
|
|
});
|
|
expect(ok).toBe(true);
|
|
});
|
|
|
|
test('bookmark short-circuit: MAX <= stored → valid without per-page work', () => {
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: { '1': 5, '2': 7 },
|
|
max_generation_at_store: 10,
|
|
};
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 10, // No writes since store
|
|
page_generations: { '1': 5, '2': 7 },
|
|
});
|
|
expect(ok).toBe(true);
|
|
});
|
|
|
|
test('single-page bumped invalidates', () => {
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: { '1': 5, '2': 7 },
|
|
max_generation_at_store: 7,
|
|
};
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 8, // Bookmark fires
|
|
page_generations: { '1': 5, '2': 8 }, // Page 2 bumped
|
|
});
|
|
expect(ok).toBe(false);
|
|
});
|
|
|
|
test('deleted page invalidates', () => {
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: { '1': 5, '2': 7 },
|
|
max_generation_at_store: 7,
|
|
};
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 8,
|
|
page_generations: { '1': 5, '2': undefined }, // Page 2 deleted
|
|
});
|
|
expect(ok).toBe(false);
|
|
});
|
|
|
|
test('multi-page partial bump invalidates', () => {
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: { '1': 5, '2': 7, '3': 9 },
|
|
max_generation_at_store: 9,
|
|
};
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 10,
|
|
page_generations: { '1': 5, '2': 7, '3': 10 }, // Only page 3 bumped
|
|
});
|
|
expect(ok).toBe(false);
|
|
});
|
|
|
|
test('codex D11 critical case (NON-empty snapshot): new page after store → Layer 1 fires → snapshot intact → row serves', () => {
|
|
// A brand-new page makes the clock advance but the cache row's
|
|
// page_generations snapshot doesn't reference it. The bookmark
|
|
// detects the corpus changed. Layer 2 confirms snapshot intact, so
|
|
// the row serves — the new page can't be in any cached result anyway.
|
|
// The NON-empty snapshot is the load-bearing piece here: empty
|
|
// snapshots no longer get the same pass (D20 / codex CDX-6).
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: { '1': 5, '2': 7 },
|
|
max_generation_at_store: 7,
|
|
};
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 8, // Page 3 was created
|
|
page_generations: { '1': 5, '2': 7 }, // Pages in snapshot unchanged
|
|
});
|
|
expect(ok).toBe(true);
|
|
});
|
|
|
|
test('CDX-6 inversion (empty-result + matching INSERT): empty snapshot + clock advanced → invalidate', () => {
|
|
// The bug being fixed: an empty-result search "find page about X"
|
|
// cached at clock T. Subsequently INSERT a matching page → clock T+1.
|
|
// Pre-v0.41.19.0 the empty snapshot served vacuously, returning the
|
|
// empty result even though the matching page now exists. Post-fix:
|
|
// invalidates so the next lookup re-queries.
|
|
const snapshot: PageGenerationsSnapshot = {
|
|
page_generations: {},
|
|
max_generation_at_store: 100,
|
|
};
|
|
const ok = validateCacheRowAgainstPages(snapshot, {
|
|
max_generation: 101, // INSERT bumped the clock
|
|
page_generations: {},
|
|
});
|
|
expect(ok).toBe(false);
|
|
});
|
|
});
|
|
|
|
describe('buildPageGenerationsSnapshot (PGLite-backed)', () => {
|
|
let engine: PGLiteEngine;
|
|
|
|
beforeAll(async () => {
|
|
engine = new PGLiteEngine();
|
|
await engine.connect({});
|
|
await engine.initSchema();
|
|
});
|
|
|
|
afterAll(async () => {
|
|
await engine.disconnect();
|
|
});
|
|
|
|
beforeEach(async () => {
|
|
await resetPgliteState(engine);
|
|
});
|
|
|
|
test('empty pageIds: snapshot has empty page_generations, MAX bookmark only', async () => {
|
|
// Seed a page so MAX > 0.
|
|
await engine.putPage('test/p1', {
|
|
type: 'note',
|
|
title: 'p1',
|
|
compiled_truth: 'body',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
const snap = await buildPageGenerationsSnapshot(engine, []);
|
|
expect(snap.page_generations).toEqual({});
|
|
expect(snap.max_generation_at_store).toBeGreaterThan(0);
|
|
});
|
|
|
|
test('populated pageIds: snapshot captures generation per page + MAX', async () => {
|
|
const p1 = await engine.putPage('test/p1', {
|
|
type: 'note',
|
|
title: 'p1',
|
|
compiled_truth: 'body1',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
const p2 = await engine.putPage('test/p2', {
|
|
type: 'note',
|
|
title: 'p2',
|
|
compiled_truth: 'body2',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
const snap = await buildPageGenerationsSnapshot(engine, [p1.id, p2.id]);
|
|
expect(Object.keys(snap.page_generations).length).toBe(2);
|
|
expect(snap.page_generations[String(p1.id)]).toBeGreaterThan(0);
|
|
expect(snap.page_generations[String(p2.id)]).toBeGreaterThan(0);
|
|
expect(snap.max_generation_at_store).toBeGreaterThanOrEqual(
|
|
Math.max(snap.page_generations[String(p1.id)], snap.page_generations[String(p2.id)]),
|
|
);
|
|
});
|
|
|
|
test('integer-typed JSONB shape regression: stored values are numbers, not strings', async () => {
|
|
const p1 = await engine.putPage('test/p1', {
|
|
type: 'note',
|
|
title: 'p1',
|
|
compiled_truth: 'body1',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
const snap = await buildPageGenerationsSnapshot(engine, [p1.id]);
|
|
const v = snap.page_generations[String(p1.id)];
|
|
expect(typeof v).toBe('number');
|
|
expect(Number.isInteger(v)).toBe(true);
|
|
});
|
|
|
|
test('non-existent pageIds: skipped (LEFT JOIN equivalent — no entry in page_generations)', async () => {
|
|
await engine.putPage('test/p1', {
|
|
type: 'note',
|
|
title: 'p1',
|
|
compiled_truth: 'body',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
// Pass two IDs: one valid, one that doesn't exist.
|
|
const rows = await engine.executeRaw<{ id: number }>(`SELECT id FROM pages LIMIT 1`);
|
|
const p1Id = rows[0].id;
|
|
const snap = await buildPageGenerationsSnapshot(engine, [p1Id, 999999]);
|
|
expect(snap.page_generations[String(p1Id)]).toBeGreaterThan(0);
|
|
expect(snap.page_generations['999999']).toBeUndefined();
|
|
});
|
|
|
|
test('after content UPDATE: generation bumps and snapshot reflects new value', async () => {
|
|
const p1 = await engine.putPage('test/p1', {
|
|
type: 'note',
|
|
title: 'p1',
|
|
compiled_truth: 'body-v1',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
const before = await buildPageGenerationsSnapshot(engine, [p1.id]);
|
|
const beforeGen = before.page_generations[String(p1.id)];
|
|
|
|
// Update compiled_truth (content allow-list column → trigger bumps).
|
|
await engine.putPage('test/p1', {
|
|
type: 'note',
|
|
title: 'p1',
|
|
compiled_truth: 'body-v2',
|
|
timeline: '',
|
|
frontmatter: {},
|
|
});
|
|
|
|
const after = await buildPageGenerationsSnapshot(engine, [p1.id]);
|
|
const afterGen = after.page_generations[String(p1.id)];
|
|
expect(afterGen).toBeGreaterThan(beforeGen);
|
|
});
|
|
});
|
|
|
|
describe('CACHE_GATE_WHERE_CLAUSE (SQL shape regression)', () => {
|
|
test('v0.41.19.0: Layer 1 reads page_generation_clock (not MAX(generation))', () => {
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain('page_generation_clock');
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain('qc.max_generation_at_store');
|
|
// Negative regression guard: the old MAX(generation) read shape MUST
|
|
// be gone (codex CDX-1/CDX-2: it silently served stale on
|
|
// UPDATE-to-non-max and DELETE).
|
|
expect(CACHE_GATE_WHERE_CLAUSE).not.toContain('MAX(generation) FROM pages');
|
|
});
|
|
|
|
test('contains Layer 2 per-page snapshot (jsonb_each + LEFT JOIN)', () => {
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain('jsonb_each(qc.page_generations)');
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain('LEFT JOIN pages');
|
|
});
|
|
|
|
test('v0.41.19.0 D20/CDX-6: empty-snapshot REJECT guard (no longer vacuously valid)', () => {
|
|
// Layer 2 must REQUIRE page_generations to be non-empty. Pre-fix
|
|
// shape was `qc.page_generations = '{}'::jsonb OR NOT EXISTS(...)`
|
|
// which let empty snapshots survive any clock bump.
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain(`qc.page_generations <> '{}'::jsonb`);
|
|
expect(CACHE_GATE_WHERE_CLAUSE).not.toMatch(/qc\.page_generations = '\{\}'::jsonb\s*OR/);
|
|
});
|
|
|
|
test('per-page mismatch path checks both deletion (NULL) and bump (!=)', () => {
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain('p.id IS NULL');
|
|
expect(CACHE_GATE_WHERE_CLAUSE).toContain('p.generation <>');
|
|
});
|
|
});
|