Repository navigation
test(release): realign hard-lease inventory and pin the catalog build bound in #11759 test - #15827
Merged
Merged
Conversation
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two base-reds on the pure
release/v3.8.52tip, reproduced there (not caused by any open PR):hard-session-lease-bypass-inventory— inventory drifted:src/app/api/v1/web/map/route.ts(new in feat(api): add Firecrawl Map endpoint with account fallback #15703) callsgetProviderCredentialsWithQuotaPreflightexactly likeweb/fetch→ listed as credential site, class B (same as web/fetch).src/lib/db/providers.tsgained a 4thgetProviderConnectionById— the priority-0 move-to-top edit path re-reads the row afterreorderConnections(fix(db): preserve explicit provider priorities on edit #15485) — count 3 → 4, same file classification.11759-embedding-registry-width-and-type— on a loaded host the cold/v1/modelsbuild exceeds the 8sCATALOG_BUILD_TIMEOUT_MSdefault and the route answers 503catalog_build_timeout(fix(models): return 503 with Retry-After when a cold catalog build exceeds its time bound #13438). The test asserts catalog contents, not the time bound, so it pinsCATALOG_BUILD_TIMEOUT_MS=180000(via??=, an explicit env still wins). Reproduced: 0/2 at default on the tip under load, 2/2 with the bound.Not touched:
chat-noauth-model-cooldown"no server-side wait inside a combo" (wall-clock < 1500 ms) also fails on the tip under load 40–50; that assertion IS the behavior under test, so it is left as is (load flake to recheck on an idle host).Validation: both files 5/5 pass; changelog-integrity 0.