Skip to content
This repository has been archived by the owner on Nov 18, 2021. It is now read-only.

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

Open
cirosantilli opened this issue Sep 4, 2018 · 2 comments
Open

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

cirosantilli opened this issue Sep 4, 2018 · 2 comments

Comments

@cirosantilli
Copy link
Collaborator

cirosantilli commented Sep 4, 2018

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".

@ghost
Copy link

ghost commented May 21, 2019

I can't push 100k commit octopus merge to GitLab did you face it @cirosantilli?

@cirosantilli
Copy link
Collaborator Author

@yocorn never tried! :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.