feat(openfeature): decrease default initialization timeout to 10s [backport 4.9] - #18177
Merged
Conversation
brettlangdon
added
the
changelog/no-changelog
brettlangdon
requested review from
greghuels,
juanjux,
rachelyangdog and
sameerank
and removed request for
a team
May 19, 2026 19:25
Codeowners resolved as |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 519a469521
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
sameerank
approved these changes
May 19, 2026
…8169) <!-- Provide an overview of the change and motivation for the change --> We found that 30s timeout doesn't play well with gunicorn, which has 30s initialization timout for the worker. If the user naively calls `openfeature.api.set_provider()` at the top-level, RC failing to deliver configuration may bring their whole application down with hard-to-debug `[CRITICAL] WORKER TIMEOUT` error message. Decrease default timeout to 10s, which is enough when RC is working but not too long to cause other issues/upstream timeouts. <!-- Describe your testing strategy or note what tests are included --> <!-- Note any risks associated with this change, or "None" if no risks --> <!-- Any other information that would be helpful for reviewers --> Part of incident-54756, follow up to #16650 Co-authored-by: brett.langdon <brett.langdon@datadoghq.com> (cherry picked from commit 017bc2a)
brettlangdon
force-pushed
the
brettlangdon/backport.18169.4.9
branch
from
May 19, 2026 19:27
519a469 to
bda1755
Compare
brettlangdon
enabled auto-merge (squash)
May 19, 2026 19:29
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
3 participants
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.
If the user naively calls
openfeature.api.set_provider()at the top-level, RC failing to deliver configuration may bring their whole application down with hard-to-debug[CRITICAL] WORKER TIMEOUTerror message.Decrease default timeout to 10s, which is enough when RC is working but not too long to cause other issues/upstream timeouts.
Part of incident-54756, follow up to https://github.com//pull/16650