1. 13 5月, 2016 1 次提交
  2. 10 5月, 2016 5 次提交
  3. 09 5月, 2016 3 次提交
    • S
      Improve multiple branch push performance by memoizing permission checking · 4be77d0b
      Stan Hu 提交于
      If you attempt to push thousands of branches at once, the 60-second timeout
      will occur because GitAccess checking does a lot of work to check if the
      user has permission to push to a branch. This changes does two things:
      
      1. Instead of making 1 DB query per branch push, use a memoized list of protected branches to check
      2. Memoize what permissions the user has to perform on this project
      
      On a test of 10,000 branch pushes, this prevents gitlab-shell from hitting the 60-second
      timeout.
      
      Closes #17225
      4be77d0b
    • K
      WIP · 5196f8e9
      Kamil Trzcinski 提交于
      5196f8e9
    • R
      Remove `wall_enabled` field from Project · 0e29653f
      Robert Speicher 提交于
      0e29653f
  4. 07 5月, 2016 1 次提交
  5. 06 5月, 2016 1 次提交
  6. 04 5月, 2016 3 次提交
  7. 30 4月, 2016 2 次提交
    • Y
      Tweak checking branches in Project#open_branches · b6a18f10
      Yorick Peterse 提交于
      This changes 4 things:
      
      1. Project#protected_branches_names has been renamed to
         Project#protected_branch_names.
      
      2. Project#open_branches uses a Set for the branch names as checking
         values in a Set is faster than checking values in a (large) Array.
      
      3. Some redundant code in Project#open_branches has been removed.
      
      4. Project#protected_branch_names now uses #pluck instead of #map,
         removing the need for loading entire DB records into memory.
      b6a18f10
    • Y
      Use a query in Project#protected_branch? · e28d1fa3
      Yorick Peterse 提交于
      This changes Project#protected_branch? to use a query to check if a
      branch is protected, instead of loading all ProtectedBranch records into
      memory just to check if the list of names includes a given branch name.
      e28d1fa3
  8. 29 4月, 2016 2 次提交
  9. 25 4月, 2016 1 次提交
  10. 19 4月, 2016 2 次提交
  11. 17 4月, 2016 1 次提交
  12. 13 4月, 2016 1 次提交
  13. 12 4月, 2016 2 次提交
  14. 07 4月, 2016 3 次提交
  15. 01 4月, 2016 3 次提交
  16. 30 3月, 2016 1 次提交
  17. 23 3月, 2016 2 次提交
  18. 22 3月, 2016 5 次提交
  19. 21 3月, 2016 1 次提交