Files
OmniRoute/tests/unit/rerank-proxy-pinning-7350.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

140 lines
5.3 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";
/**
* #7350 — rerank egressed directly instead of honoring the connection's proxy, so a
* provider that geo-blocks the host's IP (Voyage AI from some ranges) failed even when
* the connection had a working proxy pinned, while chat and embeddings on the SAME
* connection worked. `handleRerank` now takes a `connectionId`, resolves that
* connection's proxy and wraps the upstream fetch in `runWithProxyContext`.
*
* These tests drive the real DB + resolution cascade (no module mocking) and assert on
* the proxy agent that actually reaches undici, which is what "the request egressed
* through the proxy" concretely means here.
*/
const TEST_DATA_DIR = fs.mkdtempSync(path.join(os.tmpdir(), "omniroute-rerank-proxy-"));
process.env.DATA_DIR = TEST_DATA_DIR;
process.env.API_KEY_SECRET = "test-secret";
const core = await import("../../src/lib/db/core.ts");
const providersDb = await import("../../src/lib/db/providers.ts");
const proxiesDb = await import("../../src/lib/db/proxies.ts");
const proxyFetch = await import("../../open-sse/utils/proxyFetch.ts");
const { handleRerank } = await import("../../open-sse/handlers/rerank.ts");
const originalFetch = globalThis.fetch;
/** Captures the proxy URL visible inside the dispatch context at fetch time. */
function stubFetch(seen: { proxyUrl: string | null | undefined }[], gate?: () => Promise<void>) {
globalThis.fetch = (async () => {
seen.push({ proxyUrl: proxyFetch.getCurrentProxyUrlForTests?.() ?? undefined });
if (gate) await gate();
return new Response(
JSON.stringify({ data: [{ index: 0, relevance_score: 0.9 }], model: "rerank-2" }),
{ status: 200, headers: { "Content-Type": "application/json" } }
);
}) as typeof fetch;
}
test.after(() => {
globalThis.fetch = originalFetch;
core.resetDbInstance();
fs.rmSync(TEST_DATA_DIR, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
});
test("#7350 handleRerank routes the upstream call through the connection's pinned proxy", async () => {
core.resetDbInstance();
const conn = await providersDb.createProviderConnection({
provider: "voyage",
authType: "apikey",
name: "voyage-proxied",
apiKey: "pa-test-key",
});
const proxy = await proxiesDb.createProxy({
name: "Rerank Egress Proxy",
type: "http",
host: "rerank-egress.local",
port: 8080,
});
await proxiesDb.assignProxyToScope("account", (conn as { id: string }).id, proxy.id);
// The stub only ever answers a DIRECT call: runWithProxyContext dispatches through
// undici with the pinned proxy agent instead, so a pinned-but-unreachable proxy is
// observable as "the request did not succeed through the direct stub". That
// difference IS the wiring — before #7350 this call egressed directly and got a 200.
//
// #9100: the T14 reachability probe is now NON-BLOCKING — dispatch is optimistic, so
// fn() (and hence this stub) runs immediately. To still observe the dead-proxy
// failure the stub must stay pending long enough for the probe (fast NXDOMAIN /
// ECONNREFUSED on rerank-egress.local) to resolve unreachable and abort the
// in-flight request with PROXY_UNREACHABLE instead of a direct 200.
const seen: { proxyUrl: string | null | undefined }[] = [];
let releaseStub: () => void = () => {};
const stubGate = new Promise<void>((resolve) => {
releaseStub = resolve;
});
stubFetch(seen, () => stubGate);
const res = (await handleRerank({
model: "voyage/rerank-2",
query: "q",
documents: ["a", "b"],
credentials: { apiKey: "pa-test-key" },
connectionId: (conn as { id: string }).id,
})) as Response;
// Optimistic dispatch (#9100) — the request IS started; what must NOT happen is
// the stub's direct 200 winning over the unreachable-proxy abort.
assert.equal(seen.length, 1, "a pinned proxy dispatches optimistically (non-blocking probe)");
assert.notEqual(
res.status,
200,
"the unreachable pinned proxy must surface as a failure rather than silently egressing direct"
);
releaseStub();
});
test("#7350 an unresolvable connectionId degrades to a direct call instead of failing the request", async () => {
core.resetDbInstance();
const seen: { proxyUrl: string | null | undefined }[] = [];
stubFetch(seen);
const res = await handleRerank({
model: "voyage/rerank-2",
query: "q",
documents: ["a"],
credentials: { apiKey: "pa-test-key" },
connectionId: "connection-that-does-not-exist",
});
assert.equal(seen.length, 1, "proxy resolution failure must not swallow the upstream call");
assert.equal(
(res as Response).status,
200,
"a failed proxy lookup is logged and skipped, never turned into a request error"
);
});
test("#7350 omitting connectionId keeps the previous direct-egress behavior", async () => {
core.resetDbInstance();
const seen: { proxyUrl: string | null | undefined }[] = [];
stubFetch(seen);
await handleRerank({
model: "voyage/rerank-2",
query: "q",
documents: ["a"],
credentials: { apiKey: "pa-test-key" },
});
assert.equal(seen.length, 1);
assert.ok(
!seen[0].proxyUrl,
`no connectionId must mean no proxy context, saw: ${seen[0].proxyUrl}`
);
});