Compare fails with nginx 502 error when comparing branches/tags with many new commits
Created by: mjdetullio
In my GitLab 4.0 production instance, when I compare two branches, one of which is the base for the other, I get a 502 error from nginx. The second branch has approximately 450 commits on top of the first.
production.log shows everything working fine up until this last line:
Rendered commits/_text_file.html.haml (295.0ms)It does not reach the following line or start subsequent renderings
Rendered commits/_diffs.html.haml (XXX.Xms)Now I know you're asking, "why are you doing a compare on branches that are so different?" but in truth they are not that different. The project was converted from a CVS module to a Git repo, hench the large number of commits. Some of them weren't squashed during the conversion. The diff itself is between a production branch and a large development branch.
Can the compare functionality detect the size of the diff and "suppress" it like the commit view? Or expand functionality for larger diffs (not really expecting that). My users may think there is a larger issue at bay.