-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: internal provider comparison causing race conditions in tests #312
Conversation
c372d66
to
99644d2
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #312 +/- ##
==========================================
- Coverage 86.91% 86.88% -0.04%
==========================================
Files 12 13 +1
Lines 1376 1372 -4
==========================================
- Hits 1196 1192 -4
Misses 156 156
Partials 24 24
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
e21dc2f
to
3a36e19
Compare
@warber I think this solution solves the whole issue without putting constraints on the user, yes? IIUC, with this we:
Correct? |
Signed-off-by: Bernd Warmuth <bernd.warmuth@dynatrace.com>
3a36e19
to
1b18376
Compare
Hey @warber, is this still a work-in-progress or can it be reviewed now? |
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.
This PR
This pull request addresses issue #307 by comparing FeatureProvider implementations internally using their pointer addresses. It inspects the FeatureProvider provided by the user and uses the == operator for comparison if dealing with pointers. Otherwise, it utilizes the existing deepEquals comparison.
Related Issues
Fixes #307
Notes
Follow-up Tasks
How to test