3 ms·
@sytse (and @holman, now!) As of the latest Gitlab (8.8.1), my "this breaks Gitlab" commit of the Linux Kernel sources (https://gitlab.com/nrclark/dummy_projec
by nrclark 10y ago
@sytse (and @holman, now!)
As of the latest Gitlab (8.8.1), my "this breaks Gitlab" commit of the Linux Kernel sources (https://gitlab.com/nrclark/dummy_project/commit/81ebdea5df2fb42e59257cb3eaad671a5c53ca36 https://gitlab.com/nrclark/dummy_project/commit/81ebdea5df2f...) still breaks Gitlab.
When I first submitted this as a bug in December, the act of clicking on the commit would cause a Gitlab worker crash and the UI would either hang or return a 503 error. Five releases later, my sample commit still takes 10-20 seconds to load. Once it does load, it grinds my browser to a painful javascript standstill, and I have to close the tab.
Can we get some smarter diff handling on the roadmap? Please? There was a fix deployed a couple of releases ago, but the behavior is still pretty broken. :(
- sytse 10y agoThanks for the example. For me it loads slowly too (probably it has a lot of disk access) but doesn't affect the browser much. What browser are you using? I'm using Chrome on OSX. Consider creating an issue on https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues or adding it to your existing issue and linking that here.
- nrclark 10y agoHere's the issue I made a couple of months ago - https://gitlab.com/gitlab-org/gitlab-ce/issues/14775 https://gitlab.com/gitlab-org/gitlab-ce/issues/14775 As for my browser, I'm on the latest Firefox on Fedora 23. Something interesting - I think it's related to some kind of internal cache on Gitlab's side. Could I maybe get you to try loading the same page in a few hours and see what it does for you then?