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
Fixes #6785, #7180 add log delete command and make log deletion delete only based on time and not idvisit. #7887
Conversation
4a37111
to
77c3b3f
Compare
@diosmosis Sorry for the delay in getting to review this. This Pull request is high value and fixes a major bug that can lead to data loss 👍 Can you rebase it (I think work done in #7964 is relevant to this PR). After rebase let me know I will review and possibly merge. thanks |
5dfd917
to
81204da
Compare
@mattab The rebase was very complicated, tests may not pass (will have to check tomorrow). Please do a thorough review. |
…rator, and add options to delete:logs command.
…e in usercountry:attribute command. usercountry:attribute tests pass.
…n will cascade. Implement LogPurger service using different strategy from LogDataPurger (which can result in error).
…ManagerTest to pass.
…ony issue w/ using mock interactive input streams. If the posix_isatty function exists, the interactive flag set by ApplicationTester will be overridden by Application::configureIO.
…er plugin, Rename LogPurger to LogDeleter, add test for VisitorGeolocator::reattributeVisits and add empty tests for LogDeleter service.
…user desires it).
…tion step size to constructor so it can potentially be conifgured via DI, remove some unneeded TODOs.
…LogHelper and add quick class docs to LogHelper.
…gDao::insertActionsToKeep.
…nts. Also allow IntegrationTests to override DI config for tests.
…sits are tracked in the past.
81204da
to
c94a8c2
Compare
@@ -86,6 +88,15 @@ public function setUp() | |||
self::restoreDbTables(self::$tableData); | |||
} | |||
|
|||
$extraDefinitions = $this->provideContainerConfig(); |
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.
Is this change expected to be in this pull request (it seems unrelated). Either way, if the code is correct, it's fine to have it here, just double checking
…isplay when ALL websites logs are deleted, reuse OPTIMIZE table core logic
Looks good to me: cleaning up some tech debt, adding useful new command and fixing possibly major bug all at once. Took me long time to review it and test it but my tests worked 👍 |
This PR fixes #6785 and #7180. It introduces a new
logs:delete
command and makes all visit deletion (including the log data purger used by PrivacyManager) visit based on required criteria instead of the max idvisit.List of changes:
logs:delete
and LogDataPurger in PrivacyManager.usercountry:attribute
command. The looping logic was also moved to VisitorGeolocator, a late finishing touch for the command.TODO:
[ ] tests for new RawLogDao methods