Skip to content

Geo repository verification gets stuck after 1000 failed repositories

What does this MR do?

On Geo, when querying for repositories to verify, we now ignore repositories/wikis that have previously failed verification.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

Once there are a 1000 (the query batch size) verification failed repositories/wikis, the query would return the same set of records over and over, not moving forward.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • [-] Documentation created/updated
  • [-] API support added
  • Tests added for this feature/bug
  • Review
    • [-] Has been reviewed by UX
    • [-] Has been reviewed by Frontend
    • Has been reviewed by Backend
    • Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • [-] Internationalization required/considered
  • [-] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #5420 (closed)

Edited by Nick Thomas

Merge request reports