Repository navigation
Expose cause of initialization errors #6
Description
Is your feature request related to a problem? Please describe.
The Client provides an initialized_async method to wait until it has completed initialization. The function returns false if an error occurs, but there doesn't seem to be a way to access the error for logging purposes. This could make it a challenge to debug initialization issues.
Describe the solution you'd like
A more idiomatic interface in Rust would be to have initialized_async return something like Result<(), InitError> and define an InitError type to describe the different failure conditions that might arise.
Describe alternatives you've considered
A separate method could be used to retrieve the error (e.g., returning Option<InitError>.
Activity
keelerm84 commentedon Feb 16, 2022
Thank you for the feedback! I have filed this request internally as sc-142483.
Merge pull request #6 from launchdarkly/ezrastevens/ch102632/rust-sdk…
aalexandrov commentedon Dec 13, 2022
👍 for this.
gabriel-lima commentedon Jun 14, 2023
+1 for this, I am having an unknown issue which for some reason client is not initializing.
saks commentedon Jun 15, 2023
Experiencing the same issue, we had to spend quite a bit of time debugging and only found an issue once enabled
TRACElogs. Would be great to have an explicit error returned when SDK key is wrong, or any other error happened (like timeout, etc).