Files
OmniRoute/tests/unit/synced-model-delete-custom-sibling.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

109 lines
4.1 KiB
TypeScript

/**
* Model deletion is physical, while persistent exclusion uses isHidden.
*
* A custom and synced row can share one id. Deleting that id prefers the custom
* row and leaves its synced sibling intact. Deleting a synced-only row removes
* the current discovery result, but a later upstream sync may restore it.
*/
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";
// Hermetic DB: this test writes into the customModels and
// syncedAvailableModels namespaces.
const TEST_DATA_DIR = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-delete-sibling-"));
process.env.DATA_DIR = TEST_DATA_DIR;
// The DELETE route is auth-gated; with no INITIAL_PASSWORD and no stored
// credential, `isAuthenticated` resolves true for local management calls.
delete process.env.INITIAL_PASSWORD;
const core = await import("../../src/lib/db/core.ts");
const modelsDb = await import("../../src/lib/db/models.ts");
const providerModelsRoute = await import("../../src/app/api/provider-models/route.ts");
const PROVIDER = "deepseek";
const CONNECTION = "conn-delete-sibling";
const FLASH = "deepseek-v4-flash";
const PRO = "deepseek-v4-pro";
test.after(() => {
// Release the SQLite handle so the Node test runner can exit, then remove the
// throwaway DATA_DIR (CLAUDE.md "Database Handles in Tests").
core.resetDbInstance();
fs.rmSync(TEST_DATA_DIR, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
});
/** Invoke the real DELETE handler so the test tracks production behavior. */
async function deleteProviderModel(provider: string, modelId: string) {
const url =
`http://localhost/api/provider-models` +
`?provider=${encodeURIComponent(provider)}&model=${encodeURIComponent(modelId)}`;
const response = await providerModelsRoute.DELETE(new Request(url, { method: "DELETE" }));
assert.equal(response.status, 200, "DELETE /api/provider-models should succeed");
return response.json();
}
test("A: deleting a custom model leaves a same-id synced sibling re-importable", async () => {
core.resetDbInstance();
// Provider sync brings both models in; operator eye-hides one.
await modelsDb.replaceSyncedAvailableModelsForConnection(PROVIDER, CONNECTION, [
{ id: FLASH, name: FLASH },
{ id: PRO, name: PRO },
]);
modelsDb.mergeModelCompatOverride(PROVIDER, FLASH, { isHidden: true });
// Step 2 — operator manually adds a custom model with the SAME id.
await modelsDb.addCustomModel(PROVIDER, FLASH, FLASH);
// Step 3 — operator deletes the custom model they just created.
await deleteProviderModel(PROVIDER, FLASH);
// The synced sibling remains present; deleting the custom definition does not
// reinterpret the operation as a synced-model deletion.
assert.ok(
(await modelsDb.getSyncedAvailableModels(PROVIDER)).some(
(model: { id: string }) => model.id === FLASH
)
);
// The decisive assertion: a later re-sync must bring the model back.
await modelsDb.replaceSyncedAvailableModelsForConnection(PROVIDER, CONNECTION, [
{ id: FLASH, name: FLASH },
{ id: PRO, name: PRO },
]);
const ids = (await modelsDb.getSyncedAvailableModels(PROVIDER)).map((m: { id: string }) => m.id);
assert.ok(
ids.includes(FLASH),
`re-import must restore the synced model; got [${ids.join(", ")}]`
);
});
test("B: deleting a synced-only model is temporary and re-sync restores it", async () => {
core.resetDbInstance();
await modelsDb.replaceSyncedAvailableModelsForConnection(PROVIDER, CONNECTION, [
{ id: PRO, name: PRO },
]);
const result = await deleteProviderModel(PROVIDER, PRO);
assert.equal(result.removed, true);
assert.ok(
!(await modelsDb.getSyncedAvailableModels(PROVIDER)).some(
(model: { id: string }) => model.id === PRO
)
);
await modelsDb.replaceSyncedAvailableModelsForConnection(PROVIDER, CONNECTION, [
{ id: PRO, name: PRO },
]);
assert.ok(
(await modelsDb.getSyncedAvailableModels(PROVIDER)).some(
(model: { id: string }) => model.id === PRO
),
"upstream re-sync restores a physically deleted synced model"
);
});