feat: provider wrapper to support state race fix#1892
Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces a mechanism for feature providers to manage their own state, rather than the SDK managing it on their behalf. This is achieved through a new Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request introduces a StateManagingProvider interface to allow providers to manage their own state, which helps in fixing potential race conditions with state management. The FeatureProviderStateManager is updated to respect this new interface, delegating state management to the provider if it implements StateManagingProvider. The changes are logical and well-implemented. I have one suggestion to improve code quality by avoiding a call to a deprecated method.
|
|
||
| public ProviderState getState() { | ||
| if (delegateManagesState) { | ||
| return delegate.getState(); |
There was a problem hiding this comment.
The getState() method on FeatureProvider is deprecated. To avoid potential compiler warnings and to make the code clearer, it's better to cast the delegate to StateManagingProvider before calling getState(). This makes it explicit that you are using the non-deprecated method from the StateManagingProvider interface.
| return delegate.getState(); | |
| return ((StateManagingProvider) delegate).getState(); |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #1892 +/- ##
============================================
+ Coverage 92.25% 92.63% +0.37%
- Complexity 653 657 +4
============================================
Files 59 59
Lines 1589 1602 +13
Branches 179 187 +8
============================================
+ Hits 1466 1484 +18
+ Misses 76 64 -12
- Partials 47 54 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
1111da6 to
36f076d
Compare
36f076d to
94c7b9d
Compare
Signed-off-by: Todd Baert <todd.baert@dynatrace.com>
94c7b9d to
6160338
Compare
|



PoC for open-feature/spec#365. This adds a
StateManagingProviderinterface (opt-in) so providers can own their state and event emissions, fixing the race between SDK-managed state writes and provider-emitted events during/after init. When a provider implements this interface, the SDK reads state directly from the provider and skips its own state writes and event emissions in the init, shutdown, and runtime event paths. Legacy providers that do not implement the interface continue to work exactly as before (SDK manages their state). Not breaking for application-authors or provider-authors.Companion PoCs: