mirror of
https://github.com/diegosouzapw/OmniRoute.git
synced 2026-09-14 02:42:24 +03:00
e58014a41a
The unit suite base-red on release/v3.8.51 was this file, failing on a different test each run with "500 !== 200" out of getRows(). The 500 is catalog_build_timeout. Every getRows() call resets the builder, so each one is a cold full-catalog build, and that path is bounded by CATALOG_BUILD_TIMEOUT_MS (8s by default). Measured on an idle box: the cold build alone costs ~7.3s with the network stubbed out, and ~9.6s once the fire-and-forget upstream usage refreshes (api.anthropic.com, cloudcode-pa.googleapis.com, aihorde.net) land on top. The margin against the 8s bound is what decides the run, which is why the failing test moved around between runs. That budget is not the subject of this regression - canonical-mode row shaping is - so the bound is pinned out of the way, exactly as tests/unit/12627-catalog-inflight-timeout.test.ts already does for the opposite direction. No assertion is changed, removed or relaxed. Refs #12732