Files
OmniRoute/tests/unit/chatcore-executor-proxy.test.ts
Diego Rodrigues de Sa e Souza 93265eede3 test(infra): retry recursive temp-dir removal on main (main twin of #11968) (#12246)
* 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.
2026-09-01 01:48:00 -03:00

140 lines
5.2 KiB
TypeScript

// tests/unit/chatcore-executor-proxy.test.ts
// Characterization of resolveExecutorWithProxy — the upstream-proxy executor resolver extracted from
// handleChatCore (chatCore god-file decomposition, #3501). Exercises the REAL config path through a
// temp DB: disabled/native → the provider's own executor; cliproxyapi → the passthrough executor;
// fallback → a distinct wrapper that owns its own execute(). The wrapper's retry behaviour is not
// invoked here (it would hit the network); the existing cliproxyapi-fallback-wiring.test.ts covers
// the surrounding wiring.
import { test, before, after, beforeEach } 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 testDataDir = fs.mkdtempSync(path.join(os.tmpdir(), "omni-executor-proxy-test-"));
process.env.DATA_DIR = testDataDir;
// Dynamic imports AFTER DATA_DIR is set so core.ts picks up the temp path.
const coreDb = await import("../../src/lib/db/core.ts");
const upstreamProxyDb = await import("../../src/lib/db/upstreamProxy.ts");
const { resolveExecutorWithProxy } = await import(
"../../open-sse/handlers/chatCore/executorProxy.ts"
);
const { getExecutor } = await import("../../open-sse/executors/index.ts");
const { clearUpstreamProxyConfigCache } = await import(
"../../open-sse/handlers/chatCore/comboContextCache.ts"
);
before(async () => {
await coreDb.ensureDbInitialized();
});
beforeEach(() => {
clearUpstreamProxyConfigCache();
});
after(() => {
coreDb.resetDbInstance();
fs.rmSync(testDataDir, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
});
test("no config (disabled by default) returns the provider's own executor", async () => {
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai");
assert.equal(exec, getExecutor("openai"));
});
test("mode 'native' returns the provider's own executor", async () => {
await upstreamProxyDb.upsertUpstreamProxyConfig({
providerId: "openai",
mode: "native",
enabled: true,
});
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai");
assert.equal(exec, getExecutor("openai"));
});
test("mode 'cliproxyapi' returns the CLIProxyAPI passthrough executor", async () => {
await upstreamProxyDb.upsertUpstreamProxyConfig({
providerId: "anthropic",
mode: "cliproxyapi",
enabled: true,
});
clearUpstreamProxyConfigCache("anthropic");
const exec = await resolveExecutorWithProxy("anthropic");
assert.equal(exec, getExecutor("cliproxyapi"));
});
test("mode 'fallback' returns a distinct wrapper owning its own execute()", async () => {
await upstreamProxyDb.upsertUpstreamProxyConfig({
providerId: "openai",
mode: "fallback",
enabled: true,
});
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai");
assert.notEqual(exec, getExecutor("openai"));
assert.notEqual(exec, getExecutor("cliproxyapi"));
assert.equal(typeof exec.execute, "function");
});
// === Per-connection routing override (#6339) ===
// The resolved connection's providerSpecificData.cliproxyapiMode === "claude-native"
// opts THIS connection into the CLIProxyAPI executor regardless of the provider-level
// upstream_proxy_config mode. Precedence: connection override > provider mode > default.
test("connection override 'claude-native' selects CLIProxyAPI even when provider mode is native", async () => {
await upstreamProxyDb.upsertUpstreamProxyConfig({
providerId: "openai",
mode: "native",
enabled: true,
});
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai", undefined, {
cliproxyapiMode: "claude-native",
});
assert.equal(exec, getExecutor("cliproxyapi"));
});
test("connection override 'claude-native' selects CLIProxyAPI even with no provider config (default)", async () => {
clearUpstreamProxyConfigCache("anthropic");
const exec = await resolveExecutorWithProxy("anthropic", undefined, {
cliproxyapiMode: "claude-native",
});
assert.equal(exec, getExecutor("cliproxyapi"));
});
test("no connection override + provider mode native → native executor (unchanged)", async () => {
await upstreamProxyDb.upsertUpstreamProxyConfig({
providerId: "openai",
mode: "native",
enabled: true,
});
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai", undefined, {
someOtherField: "x",
});
assert.equal(exec, getExecutor("openai"));
});
test("connection override absent (undefined providerSpecificData) preserves default behaviour", async () => {
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai");
assert.equal(exec, getExecutor("openai"));
});
test("connection override wins over provider mode 'fallback'", async () => {
await upstreamProxyDb.upsertUpstreamProxyConfig({
providerId: "openai",
mode: "fallback",
enabled: true,
});
clearUpstreamProxyConfigCache("openai");
const exec = await resolveExecutorWithProxy("openai", undefined, {
cliproxyapiMode: "claude-native",
});
// Connection override short-circuits to the passthrough executor, not the fallback wrapper.
assert.equal(exec, getExecutor("cliproxyapi"));
});