Commits and Merge Requests does not list all files when one file exceeds size limits

Summary

In a merge request or commit, when viewing changed files, files that are too big are no longer listed; the user is instead left to guess about the scope of the commit or merge request.

Further, there also seems to be a file count limit; files that are shown in small-cardinality MR's can be hidden in larger MR's with more files.

I much, much prefer the old behavior of showing me all the changed files, but not expanding the changes of the big ones by default. I'd even understand banning the diff expansion for large files to preserve performance, but hiding which files were even changed is a big step back in usability of gitlab.com.

Steps to reproduce

Make a commit with changes in or addition of a large file of any type, binary or plaintext alongside a more reasonably-sized file. Look at the "Changes" tab of the commit in Gitlab.

Make a Merge Request including that commit, check that Changes tab as well.

Example Project

Look at this commit: claytonjy/overflowing-commits@dbf32e98

There were two additions, one small overflowing-commits.Rproj text file and one rather large CSV named big-tbl.csv that is just the same 32 rows repeated over and over (i.e. trivially dedupe-able).

What is the current bug behavior?

Change tabs say "1+", and will not tell you how many additional files are changed or what their names are. There appears to be no way to know that large file was changed or added, and not even the search functionality in that tab will allow you to find it.

What is the expected correct behavior?

All changed files are counted (if there's 7, say 7, not "2+") and listed in "Changes", though some may have their diffs collapsed.

Output of checks

This bug happens on GitLab.com