Skip to content
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

Repair Database does not prune old Poller Item Records #5185

Closed
TheWitness opened this issue Jan 22, 2023 · 1 comment
Closed

Repair Database does not prune old Poller Item Records #5185

TheWitness opened this issue Jan 22, 2023 · 1 comment
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Milestone

Comments

@TheWitness
Copy link
Member

Describe the bug

When you run the repair_database.php script, it does not remove orphaned poller item records.

To Reproduce

Steps to reproduce the behavior:

  1. Have many orphaned poller_items

  2. Run the repair database script

  3. Note that those poller items still exist

Expected behavior

They should be removed, and on subsequent 'full-sync' should be removed from remote data collectors.

@TheWitness TheWitness added bug Undesired behaviour unverified Some days we don't have a clue confirmed Bug is confirm by dev team and removed unverified Some days we don't have a clue labels Jan 22, 2023
@TheWitness TheWitness added this to the v1.2.24 milestone Jan 22, 2023
TheWitness added a commit that referenced this issue Jan 22, 2023
Repair Database does not prune old Poller Item Records
@TheWitness TheWitness added the resolved A fixed issue label Jan 22, 2023
@TheWitness TheWitness added the porting required Requires porting to develop label Jan 22, 2023
TheWitness added a commit that referenced this issue Jan 22, 2023
Repair Database does not prune old Poller Item Records
@TheWitness
Copy link
Member Author

Porting complete.

@TheWitness TheWitness removed the porting required Requires porting to develop label Jan 22, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Apr 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Undesired behaviour confirmed Bug is confirm by dev team resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

1 participant