An error occurred fetching the project authors.
  1. 18 Feb, 2020 1 commit
  2. 13 Feb, 2020 1 commit
  3. 12 Dec, 2019 1 commit
  4. 13 Nov, 2019 1 commit
  5. 17 Oct, 2019 1 commit
  6. 26 Jun, 2019 1 commit
    • Stan Hu's avatar
      Allow caching of negative FindCommit matches · 52215e89
      Stan Hu authored
      When FindCommit ref caching is enabled, negative matches would
      previously not be cached. However, if a source branch is deleted,
      there's no need to keep looking up the same commit. This change caches
      the result of a nil commit.
      52215e89
  7. 27 Mar, 2019 1 commit
    • Stan Hu's avatar
      Allow ref name caching CommitService#find_commit · db759c5d
      Stan Hu authored
      For a given merge request, it's quite common to see duplicate FindCommit
      Gitaly requests because the Gitaly CommitService caches the request by
      the commit SHA, not by the ref name. However, most of the duplicate
      requests use the ref name, so the cache is never actually used in
      practice. This leads to unnecessary requests that slow performance.
      
      This commit allows certain callers to bypass the ref name to
      OID conversion in the cache. We don't do this by default because it's
      possible the tip of the branch changes during the commit, which
      would cause the caller to get stale data.
      
      This commit also forces the Ci::Pipeline to use the full ref name
      so that caching can work for merge requests.
      
      Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57083
      db759c5d
  8. 17 Sep, 2018 1 commit
  9. 06 Sep, 2018 1 commit
  10. 29 Jun, 2018 1 commit
    • Sean McGivern's avatar
      Fix MR diffs created with gitaly_diff_between enabled · 2c2422d5
      Sean McGivern authored
      When we save merge request diffs to the database, we need to expand the diff
      before doing so. That's so that we can expand diffs (within the normal limits)
      without hitting the repository, but just by going to the database.
      
      This is done implicitly - diffs are expanded unless we say otherwise. However,
      we have another option we can pass, that lets us enforce diff size limits, that
      defaults to true.
      
      Prior to this commit:
      
      - The Rugged code path defaulted to setting `expanded: true` and
        `enforce_limits: true`.
      - The Gitaly code path defaulted to setting `expanded: false` and
        `enforce_limits: true`.
      
      This was introduced by eb36fa17, which
      implemented the initial feature. Since then, if the `gitaly_diff_between`
      feature flag was enabled, MRs would have diffs that could not be expanded in
      some cases, with no fix other than to disable the feature flag and force push to
      the MR to refresh the diff in the database.
      2c2422d5
  11. 12 Apr, 2018 1 commit
  12. 26 Feb, 2018 1 commit
  13. 07 Feb, 2018 1 commit
  14. 23 Jan, 2018 1 commit
  15. 03 Oct, 2017 1 commit
  16. 19 Sep, 2017 1 commit
  17. 11 Sep, 2017 1 commit
  18. 22 Aug, 2017 1 commit
  19. 21 Aug, 2017 1 commit
  20. 08 Aug, 2017 3 commits
  21. 01 Aug, 2017 1 commit
  22. 20 Jul, 2017 1 commit
  23. 19 Jul, 2017 1 commit
  24. 18 Jul, 2017 2 commits
  25. 19 Jun, 2017 1 commit
  26. 13 May, 2017 1 commit
  27. 10 May, 2017 1 commit
  28. 07 May, 2017 1 commit
  29. 07 Apr, 2017 1 commit
  30. 15 Mar, 2017 1 commit