Skip to content
代码片段 群组 项目
未验证 提交 0379621d 编辑于 作者: Evan Read's avatar Evan Read 提交者: GitLab
浏览文件

Merge branch 'alvin-master-patch-bd4d' into 'master'

Remove really old TODO items

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143996



Merged-by: default avatarEvan Read <eread@gitlab.com>
Approved-by: default avatarEvan Read <eread@gitlab.com>
Co-authored-by: default avatarAlvin Gounder <agounder@gitlab.com>
No related branches found
No related tags found
无相关合并请求
......@@ -96,9 +96,6 @@ are as follows:
- a `PoolRepository` has exactly one "source `Project`"
(`pool.source_project`)
> TODO Fix invalid SQL data for pools created prior to GitLab 11.11
> <https://gitlab.com/gitlab-org/gitaly/-/issues/1653>.
### Assumptions
- All repositories in a pool must use [hashed storage](../administration/repository_storage_paths.md).
......@@ -139,9 +136,6 @@ are as follows:
Now C gets created as a fork of B. C is not part of a pool
repository.
> TODO should forks of forks be deduplicated?
> <https://gitlab.com/gitlab-org/gitaly/-/issues/1532>
### Consequences
- If a typical Project participating in a pool gets moved to another
......@@ -195,7 +189,3 @@ then creates the pool repository in Gitaly. This leads to an
"eventually consistent" situation because as each pool participant gets
synchronized, Geo eventually triggers garbage collection in Gitaly on
the secondary, at which stage Git objects are deduplicated.
> TODO How do we handle the edge case where at the time the Geo
> secondary tries to create the pool repository, the source project does
> not exist? <https://gitlab.com/gitlab-org/gitaly/-/issues/1533>
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册