35b9274f12
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/59777. In earlier iterations of our implementation of Git object deduplication we thought we would be making extensive use of Git remotes in pool repositories in the future, and that we should manage these remotes carefully from the start. We now expect we only care about one remote, namely the source project. The other remotes are there only for forensic purposes. Before this MR we tried to also remove pool remotes when member projects got deleted, with the UnlinkRepositoryFromObjectPool RPC. This is fragile when there are race conditions (see https://gitlab.com/gitlab-org/gitaly/issues/1568#note_153955926). We have spent some time making this RPC less fragile in https://gitlab.com/gitlab-org/gitaly/merge_requests/1151 but looking at this problem again, I think we should just stop calling it. |
||
|---|---|---|
| .. | ||
| api | ||
| assets | ||
| backup | ||
| banzai | ||
| bitbucket | ||
| bitbucket_server | ||
| constraints | ||
| container_registry | ||
| declarative_policy | ||
| flowdock | ||
| generators/rails/post_deployment_migration | ||
| gitaly | ||
| gitlab | ||
| google_api | ||
| haml_lint | ||
| json_web_token | ||
| mattermost | ||
| microsoft_teams | ||
| object_storage | ||
| omni_auth/strategies | ||
| peek | ||
| quality | ||
| rouge | ||
| rspec_flaky | ||
| safe_zip | ||
| sentry | ||
| serializers | ||
| support | ||
| system_check | ||
| tasks | ||
| after_commit_queue.rb | ||
| backup.rb | ||
| banzai.rb | ||
| carrier_wave_string_file.rb | ||
| declarative_policy.rb | ||
| event_filter.rb | ||
| expand_variables.rb | ||
| extracts_path.rb | ||
| feature.rb | ||
| file_size_validator.rb | ||
| forever.rb | ||
| gitlab.rb | ||
| gt_one_coercion.rb | ||
| milestone_array.rb | ||
| mysql_zero_date.rb | ||
| static_model.rb | ||
| system_check.rb | ||
| uploaded_file.rb | ||
| version_check.rb | ||