Logs to debug duplicated pending delete_repo tasks
What does this MR do and why?
This code change adds debugging functionality to help track down issues with duplicate delete tasks in a search indexing system.
The main changes include:
- Adding detailed logging that captures the state of repositories at different stages of the deletion process
- Recording which repositories are being considered for deletion, which ones get filtered out, and their final states
- Adding a logger method to output this debugging information
- Temporarily disabling a code quality rule that normally prevents fetching unlimited database records, since this is debugging code with controlled usage
The purpose is to gather more information about why duplicate delete tasks might be occurring, so engineers can better understand and fix the underlying problem. Once the issue is resolved, this debugging code would likely be removed.
References
Screenshots or screen recordings
Before | After |
---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #547830
Edited by Ravi Kumar