Investigate the repository size calculation mechanism as repository size is stat is incorrect even after cleanup
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Repository Size Not Reflecting Correctly in GitLab.com UI
Problem Description
A customer has reported that their repository size is displaying incorrectly in the GitLab.com, even after multiple cleanup efforts (house keeping in UI). Our support engineer member with the gitlab.com admin access ran multiple attempts to refresh the repository statistics through the backend console operations, however the incorrect size persists.
Background
- Customer Ticket: https://gitlab.zendesk.com/agent/tickets/660008
- Console Escalation Request: https://gitlab.com/gitlab-com/support/internal-requests/-/issues/26758 (Update repository size shown on GUI)
- Multiple refresh attempts of the counter worker statistics have been performed without success -> Please see the comments in the above issue.
⬆️
Related Issues
This appears to be related to a previously reported issue:
- Issue #496564 (closed): "Artifact usage is inaccurate and unable to refresh through Rails Console" (October 1, 2024)
- Status: Closed
- URL: #496564 (closed)
Current Status
The incorrect repo size stats in UI persists despite the related issue being marked as closed, suggesting the problem may be more complex than initially anticipated and requires deeper investigation into the FlushCounterIncrementsWorker, repository size calculation and display mechanisms.
Request
Please investigate to determine the root cause of why repository size statistics are not updating correctly in the GitLab.com UI, even after backend refresh operations. Opening the issue for the Source Code Management team as the [FlushCounterIncrementsWorker ownership seems to have changed hands](!211119 (merged) following @daniel-prause 's advice.
Description was generated using AI