Your web UI cannot handle a mere 100k commit octopus merge #1344

• https://github.com/cirosantilli/test-octopus-100k | http://archive.is/gsR8I 500
• master: cirosantilli/test-octopus-100k@8582d01 | http://archive.is/5JwXq hangs for a while, and then cloudfare. OMG, am I / archive.is going to be blacklisted?
• one of the 100k: cirosantilli/test-octopus-100k@20c0610 | http://archive.is/xsboa works
• root: cirosantilli/test-octopus-100k@95bb02e | http://archive.is/yuQoR works
• repo generated with: https://github.com/cirosantilli/test-git-web-interface/blob/9374e5e18217982a13e354d2812d34a831ee3558/other-test-repos/many-commits-octopus.py

If the hanging page is killing your server, feel free to delete that repo while you fix the issue. I didn't think it would be that bad.

And Linus called a 66-way merge a Cthulhu merge... too young too naive: https://softwareengineering.stackexchange.com/questions/314215/can-a-git-commit-have-more-than-2-parents/377903#377903

Update 2018-11-15: https://github.com/cirosantilli/test-octopus-100k dit not 500 once for the first time. The head commit with many children took forever but did load after a few minutes! Children did not show on UI though: cirosantilli/test-octopus-100k@8582d01

Update 2019-01-13: OK, now cirosantilli/test-octopus-100k@8582d01 opens, but keeps loading the list of children forever.

Update 2019-05: nevermind, unicorn is back after a while of loading.

Update 2020-12-04: Pushing 1M failed with "Connection to github.com closed by remote host. fatal: the remote end hung up unexpectedly".