2 ms·
Tested locally on a GitLab instance: trying to push the repo results in a unicorn worker allocating ~3GB and pegging a core, then being killed on a timeout by t
by lloeki 9y ago
Tested locally on a GitLab instance: trying to push the repo results in a unicorn worker allocating ~3GB and pegging a core, then being killed on a timeout by the unicorn watchdog.
Counting objects: 18, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (17/17), done.
Writing objects: 100% (18/18), 2.13 KiB | 0 bytes/s, done.
Total 18 (delta 3), reused 0 (delta 0)
remote: GitLab: Failed to authorize your Git request: internal API unreachable
To gitlab.example.com: lloeki/git-bomb.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'git@gitlab.example.com:lloeki/git-bomb.git'
I had "Prevent committing secrets to Git" enable though. Disabling this makes the push work. The repo first then can be browsed at the first level only from the web UI, but clicking in any folder breaks the whole thing down with multiple git processes hanging onto git rev-list.
EDIT: reported at https://gitlab.com/gitlab-org/gitlab-ce/issues/39093 https://gitlab.com/gitlab-org/gitlab-ce/issues/39093 (confidential).