Todd Baert

I'm definitely in favor of this. Here is my simple reasoning: - @aepfli has proved the implementation is pretty low-effort - we've taking the time to make the file source...

cc @cpitstick-latai

I feel conflicted about this. On the one hand, I see the value and the simplicity that can be gained here for underlying SDKs that emit events. On the other...

I think I'm nearly convinced. What's your take on this? > One other question is I have is if this setting would also apply to if the init throws. Would...

OK I'm going to try to summarize so far. - The OpenFeature SDK automatically emits READY/ERROR events according to the termination of the `initialize` function - Providers support the emission...

Yes this is a great idea. We could run these as part of the SDK CI. We may also want to add something similar to the [contribs](https://github.com/open-feature/java-sdk-contrib) eventually, though there...

I'm not sure if https://github.com/open-feature/java-sdk/pull/1156 fully resolves this, but it's certainly related. @aepfli I'm happy to add a check that will check we don't have regressions with this number, but...

I think we should close this, we don't generally want to log in "hot paths" like evaluations. I'm fine with adding logging for specific, infrequent things, but I don't think...

I'm assigning this to myself; probably won't complete it but at least doing a PoC.

> Looping [@thomaspoignant](https://github.com/thomaspoignant) into this conversation. We might be able to solve this in the provider but I don't think we should change the SDK behavior. Yes I think this...