mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-08-17 20:52:15 +03:00
e44a409aa9
* fix(antigravity): classify geo-blocked egress, exclude account, real connection probe Google refuses the Cloud Code model API from unsupported egress locations with 400 FAILED_PRECONDITION "User location is not supported for the API use." Previously this surfaced as a cryptic "Antigravity upstream error (400)", never excluded the account, and the dashboard connection test stayed green because it only probed the (non-geo-restricted) OAuth userinfo endpoint. - errorClassifier: new GEO_BLOCKED type + isGeoBlockedError detection (400/403 + location-not-supported wording); non-terminal classification. - chatCore fallback: GEO_BLOCKED marks the connection and caches a 24h rate-limit-until exclusion so routing moves to other accounts instead of re-selecting the same one; never bans/expires the account. - auth: GEO_BLOCKED joins the non-terminal group (no banned/expired state). - antigravityUpstreamError: geo refusals carry an actionable message (egress location vs account problem, proxy-in-supported-region guidance). - connection test: antigravity/agy now probe the REAL streamGenerateContent surface (buildProbe), so a green tick means the model path actually works and a geo-blocked egress shows red with a clear diagnosis. * chore(changelog): fragment for #10420 antigravity geo-block resilience * chore(pr): drop prettier-version drift noise, keep only real hunks The earlier format pass (local prettier differs from the repo's pinned version) rewrapped unrelated lines in chatCore.ts and the provider test route. Restore the base formatting and re-apply only the GEO_BLOCKED fallback branch and the buildProbe connection-test changes. * fix(antigravity): strip competing-agent system prompts (429 RESOURCE_EXHAUSTED) Port decolua/9router b566b20, generalized: Antigravity flags system prompts advertising competing agents ('You are a Claude agent, built on Anthropic's Claude Agent SDK.' — Zed, Claude Code, etc.) and answers with a 429 quota error. sanitizeAntigravityGeminiRequest now strips known competitor identity sentences from systemInstruction.parts before dispatch; surrounding instruction text is untouched and non-matching prompts pass through without allocation. * chore(changelog): cover competitive prompt strip in #10420 fragment * fix(antigravity): scope GEO_BLOCKED classification to Google AI surfaces Address reviewer feedback: classifyProviderError is shared across every provider, so a lookalike 'not available in your region' body from an unrelated upstream must not receive the egress-fixable 24h exclusion treatment. Gate GEO_BLOCKED behind isGeoBlockEligibleProvider, which matches the surfaces that actually emit Google's regional-availability refusal: Cloud Code / Gemini Code Assist (antigravity, agy, cloudcode*), the Gemini Developer API (gemini, gemini-cli, vertex), plus a registry-driven fallback on executor/format. Non-Google providers fall through to their existing 400/403 classification (typically null for an unclassified 400), so a permanent block still follows its own path. * ci: re-run quality gates Trigger a fresh CI run for the PR: the previous run's 'Vitest (fast-path)' job failed in 'npm ci' because the onnxruntime-node postinstall could not download its binary from the Microsoft CDN (connect ETIMEDOUT 150.171.109.118:443). No tests ran; no code changed in this commit. * fix(antigravity): guard provider before registry lookup in geo-block gate isGeoBlockEligibleProvider passes the raw provider (string | null | undefined) to getRegistryEntry(provider: string), failing typecheck:core and the ts7-diagnostics ratchet (TS2345 at errorClassifier.ts:166). Add an explicit null guard; runtime behavior is unchanged — a falsy provider already resolved to !entry -> false. * ci: re-run quality gates (vitest npm ci onnxruntime CDN flake) --------- Co-authored-by: Rouzbeh <rqzbeh@users.noreply.github.com>
41 lines
1.9 KiB
TypeScript
41 lines
1.9 KiB
TypeScript
/**
|
|
* Build a sanitized OpenAI-style error body for a non-ok Antigravity/agy upstream
|
|
* response (#3229).
|
|
*
|
|
* The non-streaming executor path previously fed 4xx/5xx responses into the SSE
|
|
* collector, which produced a synthetic `{"object":"chat.completion","content":""}`
|
|
* success envelope — masking the real error. Route non-ok responses through
|
|
* `buildErrorBody` instead so the client sees a proper error (hard rule #12).
|
|
*/
|
|
import { buildErrorBody } from "../utils/error.ts";
|
|
import { isGeoBlockedError } from "../services/errorClassifier.ts";
|
|
|
|
// The dashboard "Test Connection" for antigravity only probes the OAuth userinfo
|
|
// endpoint (https://www.googleapis.com/oauth2/v1/userinfo), which is NOT
|
|
// geo-restricted — so a green tick does not prove the model path works. Spell
|
|
// this out in the geo-block message so operators stop chasing accounts.
|
|
const GEO_BLOCKED_HINT =
|
|
"The Cloud Code API is not offered from this server's current egress location " +
|
|
'("User location is not supported for the API use."). This is not an account ' +
|
|
"problem: the connection test only validates the Google OAuth token and does not " +
|
|
"call the model API. Route antigravity/agy egress through a proxy in a " +
|
|
"supported region (e.g. US/EU) or use a different provider.";
|
|
|
|
export function buildAntigravityUpstreamError(status: number, statusText: string, rawBody: string) {
|
|
let upstreamDetails: unknown;
|
|
try {
|
|
upstreamDetails = JSON.parse(rawBody);
|
|
} catch {
|
|
// upstream body is not JSON (e.g. HTML error page) — omit structured details
|
|
}
|
|
const suffix = statusText ? `: ${statusText}` : "";
|
|
if (isGeoBlockedError(rawBody)) {
|
|
return buildErrorBody(
|
|
status,
|
|
`Antigravity upstream error (${status})${suffix}. ${GEO_BLOCKED_HINT}`,
|
|
upstreamDetails
|
|
);
|
|
}
|
|
return buildErrorBody(status, `Antigravity upstream error (${status})${suffix}`, upstreamDetails);
|
|
}
|