Todd Baert

> Hey @guidobrei ... so the reason the e2e test is failing here is that we restart the "unstable" container too fast - it's not down long enough for your...

Wow... so [this](https://grpc.github.io/grpc/core/md_doc_connection-backoff.html) is illuminating. Apparently, deadlines can impact the reconnect logic of the underlying CONNECTION (not stream). gRPC has an underlying connection retry mechanism independent of the stream reconnect....

Could you inject your backoff stuff into the `EventStreamObserver.java` (for the RPC resolver) and take advantage of the same logging/eventing rules there too, for consistency (meaning immediately and silently retry...

@guidobrei I updated this by rebasing on main, sorry! `git reset --hard HEAD~10 && git pull` should sync your local branch back up with this.

I have a few nits but fundamentally agree. Once we merge this I will create some issues.

I will create some issues out of this.

@pradeepbbl I've created https://github.com/open-feature/java-sdk-contrib/issues/995 and https://github.com/open-feature/go-sdk-contrib/issues/585. Please confirm they make sense to you, and feel free to comment on them if you'd like to work in them.

@pradeepbbl also: https://github.com/open-feature/community/pull/397

@aepfli sorry, I started typing without selecting the textbox first and accidently closed the issue :sweat_smile: To summarize my alternative proposal: - use https://flagd.dev/schema/v0/flags.json to validate the whole document, on...

Regarding releases, we already have a CHANGELOG and release-please, which automates things related to new features, etc. We also have the flagd slack channel for other things, and a flagd...