fix(config): abort config fetch at 12s, not 5s - #875
Merged
Conversation
DEMI on Flex Consumption cold-starts in more than 5s. eao-nginx now gives up at 11s on /demi-search/config (PR #67), so the browser must abort after nginx or the first paint waits for a retry.
danieltruong
requested review from
Ckoelewyn,
tolkamps1 and
tom0827
as code owners
September 10, 2026 23:25
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
1 participant
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.
The DEMI Function on Flex Consumption cold-starts in more than 5 s. With a 5 s abort the first
/demi-search/configfetch after idle failed and first paint waited for the retry.Per-attempt abort goes from 5 s to 12 s. eao-nginx PR #67 raises its read timeout on that route to 10 s (1 s connect, 11 s worst case), so nginx still gives up before the browser. Attempts stay at 3. New spec asserts the abort is longer than nginx's 11 s.
Seen 2026-09-10 23:04 UTC on the next site during the eagle-api scale-to-0 check.