mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-21 22:32:22 +03:00
65e81158ab
Landed with the design call resolved per the owner's pick — **option 1**: the synced store is now endpoint-agnostic (persistDiscoveredModels and managedModelImport no longer drop non-chat models at write time), and chat selectability moved to read time (auto-pool expansion in autoStrategy applies filterChatSelectableModels; the models-route projection already had its chatOnly filter). Your discovery test now passes end-to-end (3/3): /api/show capabilities persist per connection and image/embedding requests route through the advertising host. Reconciliation notes: conflicted areas merged onto the current tip (adobe discovery import, requestedModel preflight signature, resolvedProvider fast-path coexists with the synced-route override — explicit resolution wins); carried base-red drains (#10055 memoization, #11071 test variants) dropped as already-landed; the managed-model-import exclusion test was propagated to the new contract (image/video models persist; the read filter still hides them from chat pickers — pinned by a new assertion). Full battery: 205/206 focused (the one red is a confirmed periodic-timer timing flake on the loaded devbox — 20/20 isolated), autoCombo vitest 30/30, combo suites 46/46, gates + typecheck clean. Thank you @yourspraveen — the capability probe + routing design was right; it just needed the store contract opened up. Fixes #11087.
83 lines
3.1 KiB
TypeScript
83 lines
3.1 KiB
TypeScript
/**
|
|
* A WAL never shrinks on its own: only `wal_checkpoint(TRUNCATE)` reclaims the file, and a
|
|
* long-running server never closes its DB (observed locally: a 154 MB WAL on a 143 MB base).
|
|
*
|
|
* The scheduler cannot be exercised directly in a unit test: it gates itself off under
|
|
* `isAutomatedTestProcess()`, same as the pre-existing DB health-check scheduler it is
|
|
* modeled on (see tests/unit/lib/jobRegistry/boot-wiring.test.ts for the same constraint).
|
|
* This reads the wiring instead.
|
|
*/
|
|
import test from "node:test";
|
|
import assert from "node:assert/strict";
|
|
import fs from "node:fs";
|
|
import path from "node:path";
|
|
|
|
function readSource(relativePath: string): string {
|
|
return fs.readFileSync(path.join(process.cwd(), relativePath), "utf8");
|
|
}
|
|
|
|
const CORE_PATH = "src/lib/db/core.ts";
|
|
|
|
test("a periodic WAL truncate scheduler is started when the DB instance boots", () => {
|
|
const source = readSource(CORE_PATH);
|
|
assert.match(
|
|
source,
|
|
/startWalTruncateScheduler\(db\)/,
|
|
"getDbInstance() must start the WAL truncate scheduler alongside the DB health-check scheduler"
|
|
);
|
|
});
|
|
|
|
test("the WAL truncate scheduler runs wal_checkpoint(TRUNCATE), not a lighter mode", () => {
|
|
const source = readSource(CORE_PATH);
|
|
const fnStart = source.indexOf("function startWalTruncateScheduler");
|
|
assert.notEqual(fnStart, -1, "startWalTruncateScheduler must exist");
|
|
const fnBody = source.slice(fnStart, fnStart + 1200);
|
|
assert.match(
|
|
fnBody,
|
|
/checkpointDb\(db, "TRUNCATE"\)/,
|
|
"the scheduled checkpoint must request TRUNCATE mode — a lighter mode would not shrink the WAL file"
|
|
);
|
|
});
|
|
|
|
test("the WAL truncate scheduler is cleared on close, like the health-check scheduler", () => {
|
|
const source = readSource(CORE_PATH);
|
|
const fnStart = source.indexOf("export function closeDbInstance");
|
|
assert.notEqual(fnStart, -1, "closeDbInstance must exist");
|
|
const fnBody = source.slice(fnStart, fnStart + 300);
|
|
assert.match(fnBody, /clearDbHealthCheckScheduler\(\)/);
|
|
assert.match(
|
|
fnBody,
|
|
/clearWalTruncateScheduler\(\)/,
|
|
"closeDbInstance() must clear the WAL truncate timer so it does not outlive the DB handle"
|
|
);
|
|
});
|
|
|
|
test("the truncate interval is overridable via OMNIROUTE_WAL_TRUNCATE_INTERVAL_MS", () => {
|
|
const source = readSource(CORE_PATH);
|
|
assert.match(
|
|
source,
|
|
/OMNIROUTE_WAL_TRUNCATE_INTERVAL_MS/,
|
|
"the interval must be operator-configurable, matching OMNIROUTE_DB_HEALTHCHECK_INTERVAL_MS"
|
|
);
|
|
});
|
|
|
|
test("the scheduler self-gates the same way the DB health-check scheduler does", () => {
|
|
const source = readSource(CORE_PATH);
|
|
const fnStart = source.indexOf("function startWalTruncateScheduler");
|
|
const fnBody = source.slice(fnStart, fnStart + 300);
|
|
assert.match(
|
|
fnBody,
|
|
/isCloud \|\| isBuildPhase \|\| isAutomatedTestProcess\(\)/,
|
|
"must not run during cloud/build/test contexts, same as startDbHealthCheckScheduler"
|
|
);
|
|
});
|
|
|
|
test("the new env var is documented", () => {
|
|
const docs = readSource("docs/reference/ENVIRONMENT.md");
|
|
assert.match(
|
|
docs,
|
|
/OMNIROUTE_WAL_TRUNCATE_INTERVAL_MS/,
|
|
"docs/reference/ENVIRONMENT.md must document the new env var (check:env-doc-sync)"
|
|
);
|
|
});
|