Repository loading: returning proper error if not found
We already had good enough error responses for the case when the *storage* is not found, but it was missing for the case when the repository is not found in an existing storage. This is important, because it can actually break the landing page of some users: the Rails application does not seem to expect an unspecified Gitaly error here, but it should recover from NOT_FOUND. I've been impaired by this on dev setup after with some repository removals, but don't have anything of that kind on hand any more, which would be more reassuring. We could have a better separation in concerns, as the subsequent change in `RepositoryExists()` indicates, but that's not a blocker for the imminent release.
parent
e4074022
No related branches found
No related tags found
Please register or sign in to comment