mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-16 03:42:21 +03:00
* test(infra): retry recursive temp-dir removal on main (main twin of #11968)
`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.
* chore(scripts): carry the rm-maxretries codemod onto main alongside its output
The codemod that generated the previous commit lives in the repo on
release/v3.8.51 (added by #11968) but was never on main. Bringing it over keeps
the tool next to the change it produced, so the transformation stays
reproducible and auditable from either branch.
94 lines
3.7 KiB
TypeScript
94 lines
3.7 KiB
TypeScript
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";
|
|
|
|
// ─── Regression test for #6325 ───────────────────────────────────────────
|
|
//
|
|
// In production, `instrumentation-node.ts` (background periodic sync) and
|
|
// `src/app/api/pricing/sync/route.ts` (dashboard status endpoint) each
|
|
// `await import("@/lib/pricingSync")` from SEPARATE Next.js standalone
|
|
// webpack entries, producing SEPARATE module instances with independent
|
|
// top-level (`lastSyncTime`, `lastSyncModelCount`, `syncTimer`) state.
|
|
//
|
|
// This test simulates that scenario by importing the module twice under
|
|
// distinct specifiers (cache-busted via a query string), so each import
|
|
// gets its own top-level module state while both share the same on-disk
|
|
// SQLite DB (as they do in production). It asserts that a status read from
|
|
// a FRESH module instance still reflects a sync performed by a DIFFERENT
|
|
// module instance — i.e. sync status must be derived from persisted state,
|
|
// not from in-memory module-level variables.
|
|
|
|
const TEST_DATA_DIR = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-pricing-sync-xinst-"));
|
|
process.env.DATA_DIR = TEST_DATA_DIR;
|
|
|
|
const core = await import("../../src/lib/db/core.ts");
|
|
|
|
const originalFetch = globalThis.fetch;
|
|
|
|
function buildLiteLLMFixture() {
|
|
return {
|
|
"openai/gpt-4o": {
|
|
input_cost_per_token: 0.0000025,
|
|
output_cost_per_token: 0.00001,
|
|
litellm_provider: "openai",
|
|
mode: "chat",
|
|
},
|
|
};
|
|
}
|
|
|
|
test.after(async () => {
|
|
globalThis.fetch = originalFetch;
|
|
core.resetDbInstance();
|
|
fs.rmSync(TEST_DATA_DIR, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
|
|
});
|
|
|
|
test("manual sync history remains visible without advertising a disabled future sync", async () => {
|
|
delete process.env.PRICING_SYNC_ENABLED;
|
|
globalThis.fetch = async () =>
|
|
new Response(JSON.stringify(buildLiteLLMFixture()), {
|
|
status: 200,
|
|
headers: { "content-type": "application/json" },
|
|
});
|
|
|
|
// Instance A: simulates the background periodic-sync module instance.
|
|
const pricingSyncA = await import("../../src/lib/pricingSync.ts?instance=A");
|
|
const result = await pricingSyncA.syncPricingFromSources({
|
|
sources: ["litellm"],
|
|
dryRun: false,
|
|
});
|
|
assert.equal(result.success, true);
|
|
|
|
// Instance B: simulates the dashboard API-route module instance — a
|
|
// genuinely fresh module scope that never called syncPricingFromSources
|
|
// itself, and whose own `syncTimer`/`lastSyncTime` module vars are unset.
|
|
const pricingSyncB = await import("../../src/lib/pricingSync.ts?instance=B");
|
|
const status = pricingSyncB.getSyncStatus();
|
|
|
|
assert.equal(
|
|
status.lastSyncModelCount,
|
|
result.modelCount,
|
|
"should read model count from persisted state"
|
|
);
|
|
assert.ok(status.lastSyncModelCount > 0, "persisted model count should be non-zero");
|
|
assert.notEqual(status.lastSync, null, "should read lastSync from persisted state");
|
|
assert.equal(status.enabled, false);
|
|
assert.equal(
|
|
status.nextSync,
|
|
null,
|
|
"manual sync history must not advertise a future run when automatic sync is disabled"
|
|
);
|
|
|
|
process.env.PRICING_SYNC_ENABLED = "false";
|
|
const explicitlyDisabledStatus = pricingSyncB.getSyncStatus();
|
|
assert.equal(explicitlyDisabledStatus.enabled, false);
|
|
assert.equal(explicitlyDisabledStatus.nextSync, null);
|
|
|
|
process.env.PRICING_SYNC_ENABLED = "true";
|
|
const enabledStatus = pricingSyncB.getSyncStatus();
|
|
assert.equal(enabledStatus.enabled, true);
|
|
assert.notEqual(enabledStatus.nextSync, null);
|
|
delete process.env.PRICING_SYNC_ENABLED;
|
|
});
|