Skip to content

Resolve "Geo: Gitlab::Git::CommandError (13:exit status 128) when calculating checksums"

What does this MR do?

Returns a dummy checksum when there is no valid repository on disk.

Why was this MR needed?

Projects that there is no valid repository on disk will always be rescheduled for verification.

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
  • EE specific content should be in the top level /ee folder
  • 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 #5750 (closed)

Merge request reports