mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-13 18:32:12 +03:00
65e81158ab
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.
17 lines
1.2 KiB
JavaScript
17 lines
1.2 KiB
JavaScript
// Preloaded (via `node --import`) before open-sse/mcp-server/server.ts and its entire
|
|
// import graph evaluate. The stdio MCP transport uses stdout exclusively for JSON-RPC
|
|
// messages, but DB init (getDbInstance(), triggered as a side effect of evaluating the
|
|
// server's module graph — e.g. tool registration reading compression settings) logs via
|
|
// plain console.log. A redirect placed *inside* server.ts (even at the top of its first
|
|
// executed function) is too late: static imports are hoisted and fully evaluated before
|
|
// any of that function's own code runs, so earlier console.log calls during import-time
|
|
// side effects already escaped to the real stdout by then. Redirecting here, in a module
|
|
// that loads before server.ts is even requested, is the only point early enough to
|
|
// guarantee no startup output leaks into the JSON-RPC stream and corrupts it client-side
|
|
// (e.g. Claude Desktop: "Unexpected token 'D', \"[DB] Changi\"... is not valid JSON").
|
|
import { Console } from "node:console";
|
|
|
|
const stderrConsole = new Console({ stdout: process.stderr, stderr: process.stderr });
|
|
console.log = stderrConsole.log.bind(stderrConsole);
|
|
console.warn = stderrConsole.warn.bind(stderrConsole);
|