Files
OmniRoute/tests/unit/antigravity-missing-project-autodisable.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

91 lines
3.6 KiB
TypeScript

/**
* #11284 — Auto-disable Antigravity connections whose Cloud Code project is
* confirmed missing, so credential selection rotates to healthy siblings
* instead of re-dispatching into a guaranteed 422 on every request.
*
* Production evidence (VPS docker `omniroute`, 2026-08-24): five rows carried
* project_id="" with NO missing-project marker — nothing excluded them from
* selection, so each dispatch paid the discovery round-trip and failed.
*
* Contract: `markAntigravityMissingCloudCodeProject()` must persist the
* typed marker (errorCode/lastErrorType) AND `isActive: false` +
* `testStatus: "unavailable"` (recoverable — NOT a terminal status), while
* `persistDiscoveredAntigravityProjectId()` re-enables the row when a project
* is later discovered at request time.
*
* Run: node --import tsx/esm --test tests/unit/antigravity-missing-project-autodisable.test.ts
*/
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-ag-11284-"));
process.env.DATA_DIR = TEST_DATA_DIR;
process.env.API_KEY_SECRET = process.env.API_KEY_SECRET || "ag-11284-test-secret";
const core = await import("../../src/lib/db/core.ts");
const providersDb = await import("../../src/lib/db/providers.ts");
const {
markAntigravityMissingCloudCodeProject,
persistDiscoveredAntigravityProjectId,
} = await import("../../open-sse/services/antigravityProjectPersistence.ts");
async function resetStorage() {
core.resetDbInstance();
fs.rmSync(TEST_DATA_DIR, { recursive: true, force: true, maxRetries: 5, retryDelay: 100 });
fs.mkdirSync(TEST_DATA_DIR, { recursive: true });
}
test.after(async () => {
await resetStorage();
});
async function createConnection() {
return providersDb.createProviderConnection({
provider: "antigravity",
authType: "oauth",
name: "autodisable-test",
email: `autodisable-${Date.now()}@example.test`,
accessToken: "token",
refreshToken: "refresh",
expiresAt: new Date(Date.now() + 60_000).toISOString(),
providerSpecificData: { tier: "g1-pro-tier" },
isActive: true,
testStatus: "active",
}) as Promise<{ id: string; providerSpecificData: Record<string, unknown> }>;
}
test("confirmed-missing project disables the connection for selection", async () => {
const connection = await createConnection();
markAntigravityMissingCloudCodeProject(connection.id);
await new Promise((resolve) => setTimeout(resolve, 50));
const updated = await providersDb.getProviderConnectionById(connection.id);
assert.equal(updated?.isActive, false, "selection must skip disabled accounts");
assert.equal(updated?.testStatus, "unavailable");
assert.equal(updated?.errorCode, "missing_project_id");
assert.equal(updated?.lastErrorType, "oauth_missing_project_id");
});
test("discovery of a projectId later re-enables the connection", async () => {
const connection = await createConnection();
markAntigravityMissingCloudCodeProject(connection.id);
await new Promise((resolve) => setTimeout(resolve, 50));
persistDiscoveredAntigravityProjectId(
connection.id,
"recovered-project-99",
connection.providerSpecificData as Record<string, unknown>
);
await new Promise((resolve) => setTimeout(resolve, 50));
const healed = await providersDb.getProviderConnectionById(connection.id);
assert.equal(healed?.projectId, "recovered-project-99");
assert.equal(healed?.isActive, true, "healthy accounts return to rotation");
assert.equal(healed?.testStatus, "active");
assert.ok(!healed?.errorCode);
});