Skip to content
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

feat: Accept timeout for LD waitForInitialization #1117

Merged

Conversation

RedbackThomson
Copy link
Contributor

@RedbackThomson RedbackThomson commented Dec 13, 2024

Add a new option to the LaunchDarkly provider constructor, initializationTimeout, which lets users optionally configure the timeout used in the LDClient waitForInitialization method. This timeout is critical because it otherwise would cause the LDClient to hang indefinitely in cases where the network connection cannot be established.

@RedbackThomson RedbackThomson requested a review from a team as a code owner December 13, 2024 18:52
@RedbackThomson RedbackThomson changed the title Accept timeout for LD waitForInitialization feat(launchdarkly): Accept timeout for LD waitForInitialization Dec 13, 2024
@kinyoklion
Copy link
Member

@RedbackThomson You will need to sign-off on your commit. You should be able to amend your commit with the signoff.

Signed-off-by: Nicholas Thomson <RedbackThomson@users.noreply.github.com>
@RedbackThomson RedbackThomson force-pushed the ld-initialization-timeout branch from 351fd14 to ff8d356 Compare December 13, 2024 18:57
@RedbackThomson
Copy link
Contributor Author

Done and force-pushed

@toddbaert toddbaert changed the title feat(launchdarkly): Accept timeout for LD waitForInitialization feat: Accept timeout for LD waitForInitialization Dec 17, 2024
@toddbaert toddbaert merged commit be7851c into open-feature:main Dec 17, 2024
6 checks passed
@toddbaert
Copy link
Member

Available with #935 merge (merging now)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants