Files
OmniRoute/tests/unit/codex-gpt55-routing-5887.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

89 lines
3.9 KiB
TypeScript

/**
* Issue #5887 — regression: an unprefixed `gpt-5.5` request from a codex-only
* setup (no OpenAI connection) stopped auto-routing to the `codex` provider.
*
* Root cause: `gpt-5.5` was added to the OpenAI static catalog
* (`open-sse/config/providers/registry/openai/index.ts`), so the
* `if (providers.includes("openai"))` short-circuit in
* `resolveModelByProviderInference` (open-sse/services/model.ts) started
* firing BEFORE the codex-preference block — making that block unreachable for
* `gpt-5.5`. Result: a codex-only user (no OpenAI connection) had `gpt-5.5`
* routed to `openai`, and Codex-only hosted image generation failed.
*
* Catalog-driven inference generalizes the original GPT-5.5-specific fix while
* preserving its compatibility boundary: Codex-only users route through Codex,
* but OpenAI remains the historical default when both providers are active.
*/
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";
const TEST_DATA_DIR = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-gpt55-5887-"));
process.env.DATA_DIR = TEST_DATA_DIR;
const core = await import("../../src/lib/db/core.ts");
const providersDb = await import("../../src/lib/db/providers.ts");
const { getModelInfoCore } = await import("../../open-sse/services/model.ts");
let openaiConnectionId: number | string | undefined;
test.after(() => {
core.resetDbInstance();
fs.rmSync(TEST_DATA_DIR, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
});
// (a) Codex active, OpenAI NOT active → bare gpt-5.5 must infer codex.
// FAILS before the fix (OpenAI static-catalog short-circuit wins).
test("#5887(a) codex-only setup infers codex for unprefixed gpt-5.5", async () => {
await providersDb.createProviderConnection({
provider: "codex",
authType: "oauth",
email: "codex@example.com",
providerSpecificData: { workspaceId: "ws-1" },
});
const info = await getModelInfoCore("gpt-5.5", null);
assert.equal(info.provider, "codex", "gpt-5.5 must infer codex when only codex is active");
// #2877: the bare id must be preserved — no `-medium` effort suffix baked in.
assert.equal(info.model, "gpt-5.5", "codex inference keeps the bare gpt-5.5 id");
});
// (b) Codex + OpenAI active → Codex wins for a Codex-native bare id.
// Reversed by #9275: `gpt-5.5` joined CODEX_NATIVE_UNPREFIXED_MODELS, so the
// ChatGPT subscription is now the deliberate destination for bare Codex CLI ids
// even with OpenAI active. The compatibility boundary this file documented moved
// from "OpenAI wins the overlap" to "an explicit prefix wins the overlap" —
// asserted in (b2) below so the override is not silently lost.
test("#5887(b) active Codex and OpenAI connections route bare gpt-5.5 to Codex", async () => {
const conn = await providersDb.createProviderConnection({
provider: "openai",
authType: "apikey",
apiKey: "sk-test",
});
openaiConnectionId = (conn as { id?: number | string })?.id;
const info = await getModelInfoCore("gpt-5.5", null);
assert.equal(
info.provider,
"codex",
"bare gpt-5.5 prefers the Codex subscription once both providers are active (#9275)"
);
assert.equal(info.model, "gpt-5.5");
});
// (b2) …but the explicit prefix stays authoritative — the documented escape hatch.
test("#5887(b2) an explicit openai/ prefix still overrides the Codex preference", async () => {
const info = await getModelInfoCore("openai/gpt-5.5", null);
assert.equal(info.provider, "openai", "explicit provider prefix beats the Codex-native set");
assert.equal(info.model, "gpt-5.5");
});
// (c) Non-regression: a normal OpenAI model still routes to openai.
test("#5887(c) gpt-4o routes to openai with openai active", async () => {
assert.ok(openaiConnectionId !== undefined, "openai connection created in (b)");
const info = await getModelInfoCore("gpt-4o", null);
assert.equal(info.provider, "openai");
});