mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-18 12:52:25 +03:00
b3f6f697ef
`main` has been red since b342c1a361 on the vitest and integration gates:
✖ tests/unit/autoCombo/provider-family-combos.test.ts > auto/<family>
✖ chat pipeline applies Codex OAuth fingerprint and priority tier inside combos
Both call resetStorage() from beforeEach, which does an fs.rmSync(TEST_DATA_DIR,
{recursive: true, force: true}) with no retry, and intermittently loses the race
with a not-yet-released SQLite handle (ENOTEMPTY).
release/v3.8.51 fixed this in #11968 with a mechanical codemod adding
maxRetries/retryDelay to every recursive rm/rmSync/rmdirSync under tests/, but
that PR landed only on the release branch. Because main only receives work at
the release squash, it stayed broken for the whole cycle — and repo-wide gates
then turn every open PR into main red on checks unrelated to their diff.
This is the --base main twin: re-runs the same codemod that already shipped on
the release branch (scripts/ad-hoc/codemod-rm-maxretries.mjs), so the two
branches converge on identical test-teardown semantics. Test-only; no product
logic is touched.
The remaining three failures reported on #12133 (unit full suite exceeding its
4800s ceiling, package-artifact exceeding 1200s, and the boot-smoke that is
skipped as a consequence) are runner-contention timeouts, not code defects —
validate-release-green.mjs runs those heavy gates concurrently on one shared
hosted runner. There is no fix to port for those.
56 lines
2.3 KiB
TypeScript
56 lines
2.3 KiB
TypeScript
/**
|
|
* A synced model delete removes the current discovery row only. If the upstream
|
|
* provider advertises that model again, the next sync restores it. Persistent
|
|
* exclusion is represented by isHidden, not a separate deletion tombstone.
|
|
*/
|
|
import test, { before, after } from "node:test";
|
|
import assert from "node:assert/strict";
|
|
import os from "node:os";
|
|
import path from "node:path";
|
|
import fs from "node:fs";
|
|
|
|
// Hermetic DB: this test mutates the syncedAvailableModels key_value namespace.
|
|
const tmpDir = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-test-synced-del-"));
|
|
process.env.DATA_DIR = tmpDir;
|
|
|
|
const { replaceSyncedAvailableModelsForConnection, getSyncedAvailableModels } =
|
|
await import("../../src/lib/localDb.ts");
|
|
const { resetDbInstance } = await import("../../src/lib/db/core.ts");
|
|
|
|
before(() => {
|
|
resetDbInstance();
|
|
});
|
|
|
|
after(() => {
|
|
resetDbInstance();
|
|
fs.rmSync(tmpDir, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
|
|
});
|
|
|
|
test("a deleted synced model is restored when upstream advertises it again", async () => {
|
|
const provider = "llama-cpp";
|
|
const connectionId = "conn-3199";
|
|
|
|
// Initial sync brings in two models.
|
|
await replaceSyncedAvailableModelsForConnection(provider, connectionId, [
|
|
{ id: "model-keep", name: "Keep" },
|
|
{ id: "model-del", name: "Delete me" },
|
|
]);
|
|
let synced = (await getSyncedAvailableModels(provider)).map((m) => m.id);
|
|
assert.ok(synced.includes("model-del"), "both models present after first sync");
|
|
|
|
const { removeSyncedAvailableModel } = await import("../../src/lib/localDb.ts");
|
|
assert.equal(await removeSyncedAvailableModel(provider, "model-del"), true);
|
|
synced = (await getSyncedAvailableModels(provider)).map((m) => m.id);
|
|
assert.ok(!synced.includes("model-del"), "delete removes the current synced row");
|
|
|
|
// Auto-fetch re-imports the SAME upstream list (still advertising model-del).
|
|
await replaceSyncedAvailableModelsForConnection(provider, connectionId, [
|
|
{ id: "model-keep", name: "Keep" },
|
|
{ id: "model-del", name: "Delete me" },
|
|
]);
|
|
|
|
synced = (await getSyncedAvailableModels(provider)).map((m) => m.id);
|
|
assert.ok(synced.includes("model-keep"), "unrelated model stays");
|
|
assert.ok(synced.includes("model-del"), "upstream re-sync restores the deleted model");
|
|
});
|