Huge commit changes produces `Data too long` error
Summary
I pushed a commit with 3272
files changed. Not really extraordinary but file paths are quite long. The push works properly but the push event is not listed in the dashboard and, much boring, the CI build wasn't triggered.
Steps to reproduce
My project is a Node.js based and (for a reason that concerns only me) I commit the installed dependencies, the node_modules
folder. This folder may contain lot of files.
Expected behavior
Push event listed in dashboard and CI build triggered.
Relevant logs and/or screenshots
Data too long for column 'data' at row 1: INSERT INTO `events` (`project_id`, `action`, `author_id`, `data`, `created_at`, `updated_at`) VALUES (518, 5, 19, '---\n:object_kind: push\n:before: 63933575
.......
Versions
System information
System: Ubuntu 14.04
Current User: git
Using RVM: no
Ruby Version: 2.1.6p336
Gem Version: 2.2.3
Bundler Version:1.9.9
Rake Version: 10.4.2
Sidekiq Version:4.0.1
GitLab information
Version: 8.3.4
Revision: 5916670
Directory: /home/git/gitlab
DB Adapter: mysql2
URL: https://gitlab.foo.be
HTTP Clone URL: https://gitlab.foo.be/some-group/some-project.git
SSH Clone URL: git@gitlab.foo.be:some-group/some-project.git
Using LDAP: no
Using Omniauth: yes
Omniauth Providers: github
GitLab Shell
Version: 2.6.9
Repositories: /home/git/repositories/
Hooks: /home/git/gitlab-shell/hooks/
Git: /usr/bin/git