-
Notifications
You must be signed in to change notification settings - Fork 780
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
refactor: introduce CacheManager #2785
refactor: introduce CacheManager #2785
Conversation
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2785 +/- ##
=========================================
Coverage ? 53.58%
=========================================
Files ? 132
Lines ? 11550
Branches ? 0
=========================================
Hits ? 6189
Misses ? 4882
Partials ? 479
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
The PR title should avoid using an abbreviation for a net-new concept (CMT) as it will make release notes harder to read |
@anlandu fyi |
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
removes todos Signed-off-by: alex <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
@@ -0,0 +1,138 @@ | |||
package cachemanager |
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.
Let's remember that config_controller_test
, by definition, tests the sync controller, which will test that the CM handles the current uses cases as well.
So the new tests here are meant to only target the cachemanager
in as much isolation as possible from controllers.
Another point to remember is that as we build the background replay process more into the cachemanager
, the tests will change to cover the new functionality.
Signed-off-by: Alex Pana <[email protected]>
@maxsmythe @ritazh @sozercan PTAL when y'all have some time! 🙏🏼 |
ping :) |
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
Signed-off-by: Alex Pana <[email protected]>
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.
LGTM
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.
Sorry for the delay, thanks! LGTM
meta
Factors out data mgmt & replication from the
sync_controller
.