Gitaly N+1 error exporting project
Attempting to export the gitlab-ce project from a local GDK install:
GitalyClient#migrate called 40 times from single request. Potential n+1? The following call site called into Gitaly 10 times: /home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/lib/gitlab/gitaly_client.rb:163:in `migrate'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/lib/gitlab/git/blob.rb:25:in `find'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/lib/gitlab/git/repository.rb:1161:in `blob_at'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/repository.rb:472:in `blob_at'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/repository.rb:1087:in `blob_data_at'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/repository.rb:1065:in `gitlab_ci_yml_for'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/ci/pipeline.rb:522:in `ci_yaml_from_repo'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/ci/pipeline.rb:417:in `ci_yaml_file'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/ci/pipeline.rb:388:in `config_processor'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/ci/build.rb:557:in `build_attributes_from_config'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/ci/build.rb:399:in `yaml_variables'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:108:in `block in serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:108:in `each'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:108:in `serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activerecord-4.2.8/lib/active_record/serialization.rb:17:in `serializable_hash'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/models/ci/build.rb:469:in `serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:114:in `block (2 levels) in serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:114:in `map'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:114:in `block in serializable_hash' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:158:in `block in serializable_add_includes' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:156:in `each' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:156:in `serializable_add_includes' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:112:in `serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activerecord-4.2.8/lib/active_record/serialization.rb:17:in `serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:114:in `block (2 levels) in serializable_hash' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:114:in `map' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:114:in `block in serializable_hash' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:158:in `block in serializable_add_includes' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:156:in `each' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:156:in `serializable_add_includes' /home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serialization.rb:112:in `serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activerecord-4.2.8/lib/active_record/serialization.rb:17:in `serializable_hash'
/home/lupine/.gem/ruby/2.3.4/gems/activemodel-4.2.8/lib/active_model/serializers/json.rb:99:in `as_json' /home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/lib/gitlab/import_export/project_tree_saver.rb:34:in `project_json'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/lib/gitlab/import_export/project_tree_saver.rb:28:in `project_json_tree'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/lib/gitlab/import_export/project_tree_saver.rb:18:in `save'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/services/projects/import_export/export_service.rb:12:in `each'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/services/projects/import_export/export_service.rb:12:in `all?'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/services/projects/import_export/export_service.rb:12:in `save_all'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/services/projects/import_export/export_service.rb:6:in `execute'
/home/lupine/dev/gitlab.com/gitlab-org/gitlab-development-kit/gitlab/app/workers/project_export_worker.rb:12:in `perform'
/home/lupine/.gem/ruby/2.3.4/gems/sidekiq-5.0.4/lib/sidekiq/processor.rb:199:in `execute_job'
# ...I've attempted to export nick.thomas/gitlab-ce on gitlab.com and haven't had a link emailed to me yet. At the same time, I don't see a matching error in sentry.