I hope this is the correct place to report a bug - please let me know if I should move this somewhere else.
My repository at https://gitlab.com/A1kmm/alertmanager-to-gotify is consistently getting a 500 internal server error - and it seems to be an ongoing issue even after trying again the next day. I don’t think I’ve done anything particularly pathological in that repo, so not entirely sure what corner case it has triggered.
Steps to reproduce: Navigate to https://gitlab.com/A1kmm/alertmanager-to-gotify in your browser. It happens consistently for this URL whether logged in as me or in private browsing with no existing GitLab cookies set.
What I expected to happen: See the UI for the repository.
What actually happened: It displayed a “500 Whoops, something went wrong on our end.” page.
5 out of my 8 projects have the same issue. They were all working previously, no change from me. And now I suddenly get the same error (500 internal server error).
As others have mentioned, if I instead go to a subpage, like for instance -/tree/master or any other subpath, then there is no problem. It only seems to affect the “home page” for a repo.
Has anyone figured out a resolution to this issue yet? One of my developers is having this issue. I’ve tried creating them a new account as well but it also has the same issue. As of now they’re using the work around to navigate to a sub-route of the project but this isn’t very good resolution.
This happened as of the patch v17.2.2 and is still occurring as of v17.3.0