Files
OmniRoute/open-sse/services/combo/comboDiagFormat.ts
Praveen K Palaniswamy 65e81158ab fix(ollama): route models by advertised capability (#11088)
Landed with the design call resolved per the owner's pick — **option 1**: the synced store is now endpoint-agnostic (persistDiscoveredModels and managedModelImport no longer drop non-chat models at write time), and chat selectability moved to read time (auto-pool expansion in autoStrategy applies filterChatSelectableModels; the models-route projection already had its chatOnly filter). Your discovery test now passes end-to-end (3/3): /api/show capabilities persist per connection and image/embedding requests route through the advertising host.

Reconciliation notes: conflicted areas merged onto the current tip (adobe discovery import, requestedModel preflight signature, resolvedProvider fast-path coexists with the synced-route override — explicit resolution wins); carried base-red drains (#10055 memoization, #11071 test variants) dropped as already-landed; the managed-model-import exclusion test was propagated to the new contract (image/video models persist; the read filter still hides them from chat pickers — pinned by a new assertion). Full battery: 205/206 focused (the one red is a confirmed periodic-timer timing flake on the loaded devbox — 20/20 isolated), autoCombo vitest 30/30, combo suites 46/46, gates + typecheck clean.

Thank you @yourspraveen — the capability probe + routing design was right; it just needed the store contract opened up. Fixes #11087.
2026-08-23 11:45:01 -03:00

30 lines
1.3 KiB
TypeScript

/**
* #10967: format an `exhaustedConnections` key stored by targetExhaustion.ts
* (`markAuthLevelExhaustion` / `markAgentrouterConnectionQuotaExhaustion` /
* `markConnectionLevelExhaustion`, all keyed as `` `${provider}:${connectionId}` ``)
* into a diagnostics `excluded` entry.
*
* Before this fix, `buildComboDiag` (combo.ts) hardcoded `provider: "unknown"` and
* `slice(0, 8)`'d the WHOLE key — for a typical `jina-ai:<uuid>` key that produced
* `exhausted_connection:jina-ai:` (the 7-char provider id + colon consumed the
* entire 8-char budget, the UUID silently dropped, and the real provider id
* discarded in favor of the literal string "unknown").
*
* Splitting on the FIRST `:` recovers the real provider id and truncates only the
* connection-id half (never the full UUID, matching the public combo projection's
* connection-id redaction policy — #2300).
*/
export function formatExhaustedConnectionKey(key: string): {
provider: string;
reason: string;
} {
const raw = String(key);
const sepIdx = raw.indexOf(":");
const provider = sepIdx >= 0 ? raw.slice(0, sepIdx) : "";
const connId = sepIdx >= 0 ? raw.slice(sepIdx + 1) : raw;
return {
provider: provider || "unknown",
reason: `exhausted_connection:${connId.slice(0, 8)}`,
};
}