Uh oh!
There was an error while loading. Please reload this page.
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.
The OpenFeature SDK will catch this exception? I want to double check that raising is the expectation.
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.
Yes — raising is the mechanism the OpenFeature Ruby SDK expects.
Configuration#init_providerwraps theinitcall in arescue, dispatchesPROVIDER_ERROR(which moves provider state toERROR), and only re-raises — asProviderInitializationError— when the caller usedset_provider_and_wait. Withset_providerthe init runs on its own thread and the exception is swallowed after the error event (v0.6.5configuration.rb):So a failed initialization ends in the
ERRORstate rather thanFATAL, matching the mapping we settled on in the spec: the LaunchDarkly client can still serve whatever data it has, so the OpenFeature SDK should keep calling the provider. Note the SDK also readserror_codeoff the exception if it exposes one, so we could raise a custom error later if we want something more specific thanGENERAL.