-
Notifications
You must be signed in to change notification settings - Fork 1
feat: Add a start wait timeout for initialization #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
83a1dcf
feat: Add a start wait timeout for initialization
devin-ai-integration[bot] 7afe073
docs: Clarify the blocking behavior of start_wait
devin-ai-integration[bot] 057a27b
fix: Resolve initialization immediately when a start wait was used
devin-ai-integration[bot] de5abc2
chore: Merge origin/main into start-wait branch
devin-ai-integration[bot] db02aac
Merge remote-tracking branch 'origin/main' into devin/1787767005-pyth…
devin-ai-integration[bot] 69390f7
docs: Mark initialization as supported in the feature matrix
devin-ai-integration[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Timeout drops later ready events
Medium Severity
When
start_waitexpires,initializeraisesProviderNotReadyErrorbefore attaching the data-source and flag listeners. A later LaunchDarkly connection never emitsPROVIDER_READY, so OpenFeature stays inERRORand configuration-change events are also dropped.Reviewed by Cursor Bugbot for commit 69390f7. Configure here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is correct, and it contradicts a bullet in the description above (now fixed): the
raisehappens before the status and flag-change listeners are attached, so a provider whose start wait lapses stays silent — noPROVIDER_READYwhen the connection later succeeds, and no configuration-changed events either. It isn't new to this PR (the same was true of the pre-existingis_initialized()failure path), but a start wait makes it reachable from mere slowness rather than only from a permanent failure.Not changing it here, since it's the same open question as on openfeature-java-server#61: whether a lapsed start wait is terminal for the provider or just a failed initialization it can recover from. Attaching the listeners before the raise is the fix if it's the latter, and it should be decided the same way in both languages.