Skip to content
Snippets Groups Projects
  1. 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
  2. Apr 14, 2018
  3. Apr 11, 2018
  4. Apr 10, 2018
  5. Apr 09, 2018
  6. Apr 07, 2018
  7. Apr 06, 2018
  8. Apr 05, 2018
  9. Apr 04, 2018
  10. Apr 03, 2018
  11. Apr 02, 2018
  12. Mar 30, 2018
  13. Mar 29, 2018
  14. Mar 28, 2018
Loading