Files
OmniRoute/tests/unit/probe-9541-repro.test.ts
Diego Rodrigues de Sa e Souza 3d4f3e4960 test(infra): retry recursive temp-dir removal instead of failing a shard on ENOTEMPTY (#11966) (#11968)
* test(infra): retry recursive temp-dir removal instead of failing a shard on ENOTEMPTY (#11966)

Two shards on release/v3.8.51 went red in one day with the same signature —
"ENOTEMPTY, Directory not empty: /tmp/omniroute-<test>-XXXXXX" — from
combo-same-provider-cascade (Unit Tests fast-path 4/4, on a PR that touches only
.github/) and auth-policy-embeddings-webfetch-7785 (the 20k-test TIA step). Both pass
alone and on re-run: the cleanup races something still writing into the directory
(SQLite WAL/-shm checkpoint, a worker, the backup) and under a loaded hosted runner
the window opens. 1154 test files do their own cleanup with
fs.rmSync(dir, { recursive: true, force: true }); 57 already asked for retries.

One-shot codemod (scripts/ad-hoc/codemod-rm-maxretries.mjs, kept for the record):
every rm / rmSync / rmdirSync option object with `recursive: true` and no
`maxRetries` gains `maxRetries: 5, retryDelay: 100` — Node itself then retries
ENOTEMPTY/EBUSY/EPERM for up to ~0.5 s before giving up. 2243 call sites in 1292
files under tests/, the shared tests/_setup/isolateDataDir.ts exit hook included.
Only the option object changes: no call site, assertion or import is touched.

Validation: prettier and ESLint (with the frozen suppressions) clean on all 1292
files; a random 20-file sample runs green (quota-redis-store hangs identically on
the untouched tree — it needs a Redis on localhost, an environment matter). The
four unit shards on this PR are the full run.

* fix(quality): let check-forgotten-sibling-tests read a 1,000-file diff

The gate shells out to `git diff` through execFileSync with Node's default 1 MB
maxBuffer; the 1,292-file codemod in this PR is the first diff large enough to
overflow it, and the gate died with `spawnSync git ENOBUFS` before comparing
anything. 64 MB is far above any real PR and costs nothing when unused.
2026-08-29 01:17:40 -03:00

136 lines
5.0 KiB
TypeScript

// TDD verification for #9541 — DB corruption probe transient-error retry.
//
// RED: The repro confirms transient errors (BUSY, ENOENT, PROTOCOL, IOERR)
// fall through to the corruption-rename path (data loss confirmed).
// GREEN: After the fix, isTransientProbeError() exists in core.ts and correctly
// classifies transient vs fatal errors, and a retry loop prevents immediate
// corruption declaration.
import test from "node:test";
import assert from "node:assert/strict";
import fs from "node:fs";
import os from "node:os";
import path from "node:path";
// Import the fix function from probeUtils.ts
const probeUtils = await import("../../src/lib/db/probeUtils.ts");
// ── Tests from the original probe that confirmed the bug ──
test("FIX-GREEN: isTransientProbeError is exported and classifies BUSY", () => {
const busy = new Error("SQLITE_BUSY: database is locked");
// The fix must exist
assert.equal(
typeof probeUtils.isTransientProbeError,
"function",
"isTransientProbeError must be exported from core.ts"
);
assert.equal(probeUtils.isTransientProbeError(busy), true, "BUSY is transient");
});
test("FIX-GREEN: isTransientProbeError does NOT classify fatal errors", () => {
const fatalPatterns = [
"out of memory",
"allocation failure",
"Array buffer allocation failed",
"could not be found",
"Module did not self-register",
];
for (const msg of fatalPatterns) {
assert.equal(
probeUtils.isTransientProbeError(new Error(msg)),
false,
`fatal should NOT be transient: ${msg}`
);
}
});
test("FIX-GREEN: isTransientProbeError classifies BUSY/PROTOCOL/IOERR/ENOENT", () => {
const transientPatterns = [
"SQLITE_BUSY: database is locked",
"SQLITE_PROTOCOL: locking protocol",
"SQLITE_IOERR: disk I/O error",
"ENOENT: no such file or directory, open '/tmp/db.sqlite'",
];
for (const msg of transientPatterns) {
assert.equal(probeUtils.isTransientProbeError(new Error(msg)), true, `transient: ${msg}`);
}
});
test("FIX-GREEN: isTransientProbeError handles non-Error input gracefully", () => {
assert.equal(probeUtils.isTransientProbeError("SQLITE_BUSY"), true, "string error works");
assert.equal(
probeUtils.isTransientProbeError("random string"),
false,
"non-matching string returns false"
);
assert.equal(probeUtils.isTransientProbeError(null), false, "null returns false");
assert.equal(probeUtils.isTransientProbeError(undefined), false, "undefined returns false");
assert.equal(probeUtils.isTransientProbeError({}), false, "object without message returns false");
});
test("BUG-CONFIRMED (regression guard): probe failure renames DB and loses persisted config", () => {
// This test confirms the SCENARIO we're preventing — if the probe path is
// reached (all transient retries exhausted or non-transient), data IS lost.
// This is the EXISTING behavior on non-transient errors; the fix only
// ADDED a retry window for transient errors before this path.
const dir = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-9541-data-loss-"));
const sqliteFile = path.join(dir, "storage.sqlite");
try {
const header = Buffer.alloc(100);
header.write("SQLite format 3\0");
fs.writeFileSync(sqliteFile, header);
fs.writeFileSync(sqliteFile, "DATA_MARKER_PERSISTED_CONFIG", { flag: "a" });
const beforeContent = fs.readFileSync(sqliteFile, "utf-8");
assert.ok(
beforeContent.includes("DATA_MARKER_PERSISTED_CONFIG"),
"data must be present before probe failure"
);
// Simulate probe failure: rename + create new empty DB
const failedPath = sqliteFile + `.probe-failed-${Date.now()}`;
fs.renameSync(sqliteFile, failedPath);
const newHeader = Buffer.alloc(100);
newHeader.write("SQLite format 3\0");
fs.writeFileSync(sqliteFile, newHeader);
const afterContent = fs.readFileSync(sqliteFile, "utf-8");
assert.equal(
afterContent.includes("DATA_MARKER_PERSISTED_CONFIG"),
false,
"data MUST be lost when DB is renamed and recreated (corruption path behavior)"
);
} finally {
try {
fs.rmSync(dir, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
} catch {
/* ok */
}
}
});
test("FIX-GREEN: DATA_DIR no longer overridden at module scope in probe-9033-repro", async () => {
// Verify the fix in probe-9033-repro.test.ts no longer sets process.env.DATA_DIR
// at module scope. Read-only accesses to process.env.DATA_DIR are fine.
const reproTestSource = fs.readFileSync(
new URL("../../tests/unit/authz/probe-9033-repro.test.ts", import.meta.url),
"utf-8"
);
// Find lines that ASSIGN to process.env.DATA_DIR (not just read it)
const assignLines = reproTestSource
.split("\n")
.filter((line) => /process\.env\.DATA_DIR\s*=/.test(line) && !line.trim().startsWith("//"));
assert.equal(
assignLines.length,
0,
`probe-9033-repro must not assign process.env.DATA_DIR at module scope. Found: ${assignLines.map((l) => l.trim()).join(", ")}`
);
});