- Aug 01, 2018
-
-
Jamie Schembri authored
-
- Jul 26, 2018
-
-
gfyoung authored
Partially addresses #47424.
-
- Jul 25, 2018
-
-
Tiago Botelho authored
-
Tiago Botelho authored
Backports relevant changes made in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5163 to CE
-
- May 28, 2018
-
-
Andreas Brandl authored
This was needed for a transition phase only. For details see #45389. Closes #45389.
-
- May 03, 2018
-
-
Shinya Maeda authored
-
- Apr 20, 2018
-
-
Andreas Brandl authored
-
- Apr 16, 2018
-
-
Andreas Brandl authored
This is useful for a transition period to migrate away from `NoninternalAtomicId`. In a situation where both the old and new code to generate a iid value is run at the same time (for example, during a deploy different nodes may serve both versions), this will lead to problems regarding the correct `last_value`. That is, what we track in `InternalId` may get out of sync with the maximum iid present for issues. With this change, we double-check that and correct the `last_value` with the maximum iid found in issues if necessary. This is subject to be removed with the 10.8 release and tracked over here: https://gitlab.com/gitlab-org/gitlab-ce/issues/45389 Closes #45269.
-
- Mar 16, 2018
-
-
Andreas Brandl authored
-
Andreas Brandl authored
-
Andreas Brandl authored
The specs are based on a schema version that doesn't know about `internal_ids` table. However, the actual code being execute relies on it.
-
Andreas Brandl authored
-
Andreas Brandl authored
-
Andreas Brandl authored
-