Stop rescuing Rugged::Reference in Repository cache
What does this MR do?
Removes a Rugged-specific rescue from the cache mechanism on Repository. If I understand this correctly, the impact is that in theory some cases where we would show an empty page might start throwing an exception instead. But as far as I can see, I have caught the only place where we could still be throwing Rugged::ReferenceError.
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
We want to decouple the application from Rugged.
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 -
End-to-end tests pass ( package-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Jacob Vosmaer