mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-18 04:42:30 +03:00
b6975537c1
* fix(providers): remove the chipotle/pepper provider (#13131) amelia.chipotle.com (the reverse-engineered Amelia chat-widget backend chipotle/pepper-1 talked to) now returns 404 on every route, including root, from its Azure Application Gateway — confirmed live 2026-09-15. This regressed from a WS handshake timeout (#4037, June 2026) to a fully decommissioned host, so the upstream protocol cannot be fixed. Owner decided to retire the provider entirely (Option B), following the phind/kluster quiet-removal precedent: no REMOVED_PROVIDERS.md entry (reserved for operator takedowns), just a one-line note under FREE_TIERS.md "Removed / no free tier". Removed every surface: executor, registry entry, executors/index.ts and providers/index.ts wiring, noauth provider catalog entry, ProviderIcon generic-fallback set, the autoCombo exclusion-list comment, the chipotle_error code from the sanitizer allowlist, PROVIDER_REFERENCE.md (regenerated), and every doc/test reference. Regression test: tests/unit/issue-13131-chipotle-provider-removed.test.ts asserts the provider is fully gone from the executor registry, the provider REGISTRY and the noauth catalog, and that the executor module no longer resolves — not a live-network repro (flaky/third-party). Several existing tests used "chipotle" only as a generic noAuth-provider example (proxy scoping, error classification, onboarding, fallback text) with no chipotle-specific behavior under test; those were re-pointed at another still-existing noAuth provider (cloudflare-playground / duckduckgo-web) rather than weakened. * test(providers): document the agnes-cn/chipotle count coincidence (#13131) provider-node-reserved-prefix.test.ts's REGISTRY id+alias walk was already red on the base tip (414 vs. expected 412) from agnes-cn (#13399, +id/+alias). Removing chipotle's REGISTRY id/alias in this PR nets it back to 412, making the test pass again without a numeric edit — record why in a comment so it doesn't read as an untracked coincidence later.
20 lines
1023 B
TypeScript
20 lines
1023 B
TypeScript
import test from "node:test";
|
|
import assert from "node:assert/strict";
|
|
import { classifyProviderError } from "../../open-sse/services/errorClassifier.ts";
|
|
|
|
// #6315 / #6345 — a single generic upstream 403 on a no-credential ("authType:
|
|
// none") provider was permanently banning the whole
|
|
// connection (classified as FORBIDDEN, a terminal type). These providers are
|
|
// free/stateless — there is no real account/credential to revoke, so a bare
|
|
// 403 should be RECOVERABLE (null) and handled by the existing connection
|
|
// cooldown/retry layer, same as apikey providers already are.
|
|
|
|
test("#6345: no-credential provider 'Request blocked'/access_denied 403 -> recoverable (null), not FORBIDDEN", () => {
|
|
const body = { error: "Request blocked", type: "access_denied" };
|
|
assert.equal(classifyProviderError(403, body, "duckduckgo-web"), null);
|
|
});
|
|
|
|
test("control: apikey-provider bare 403 still recoverable (null) — no regression", () => {
|
|
assert.equal(classifyProviderError(403, "forbidden", "openai"), null);
|
|
});
|