Skip to content
Snippets Groups Projects
  1. Aug 01, 2018
  2. Jul 26, 2018
  3. Jul 25, 2018
  4. May 28, 2018
  5. May 03, 2018
  6. Apr 20, 2018
  7. Apr 16, 2018
    • Andreas Brandl's avatar
      Double-check next value for internal ids. · 14acbf24
      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.
      14acbf24
  8. Mar 16, 2018
Loading