BigW Consortium Gitlab

  1. 06 Dec, 2017 1 commit
    • Throttle the number of UPDATEs triggered by touch · 856447cc
      Yorick Peterse authored
      This throttles the number of UPDATE queries that can be triggered by
      calling "touch" on a Note, Issue, or MergeRequest. For Note objects we
      also take care of updating the associated "noteable" relation in a
      smarter way than Rails does by default.
  2. 13 Nov, 2017 1 commit
  3. 11 Nov, 2017 1 commit
  4. 09 Oct, 2017 2 commits
  5. 30 Aug, 2017 1 commit
  6. 23 Aug, 2017 1 commit
    • Cache the number of open issues and merge requests · 6ec53f5d
      Yorick Peterse authored
      Every project page displays a navigation menu that in turn displays the
      number of open issues and merge requests. This means that for every
      project page we run two COUNT(*) queries, each taking up roughly 30
      milliseconds on GitLab.com. By caching these numbers and refreshing them
      whenever necessary we can reduce loading times of all these pages by up
      to roughly 60 milliseconds.
      
      The number of open issues does not include confidential issues. This is
      a trade-off to keep the code simple and to ensure refreshing the data
      only needs 2 COUNT(*) queries instead of 3. A downside is that if a
      project only has 5 confidential issues the counter will be set to 0.
      
      Because we now have 3 similar counting service classes the code
      previously used in Projects::ForksCountService has mostly been moved to
      Projects::CountService, which in turn is reused by the various service
      classes.
      
      Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36622
  7. 11 Aug, 2017 1 commit
  8. 09 Aug, 2017 1 commit
  9. 07 Aug, 2017 1 commit
  10. 02 Aug, 2017 1 commit
  11. 01 Aug, 2017 1 commit
  12. 27 Jul, 2017 1 commit
  13. 21 Jun, 2017 1 commit
  14. 14 Jun, 2017 1 commit
  15. 12 May, 2017 1 commit
  16. 04 May, 2017 2 commits
  17. 20 Apr, 2017 1 commit
  18. 10 Apr, 2017 1 commit
  19. 04 Apr, 2017 1 commit
  20. 21 Mar, 2017 1 commit
  21. 17 Mar, 2017 1 commit
  22. 14 Mar, 2017 2 commits
  23. 23 Feb, 2017 2 commits
  24. 27 Jan, 2017 3 commits
  25. 26 Jan, 2017 1 commit
  26. 25 Jan, 2017 1 commit
  27. 03 Jan, 2017 1 commit
  28. 15 Dec, 2016 1 commit
  29. 02 Dec, 2016 1 commit
  30. 23 Nov, 2016 1 commit
  31. 09 Nov, 2016 1 commit
  32. 20 Oct, 2016 1 commit
  33. 28 Sep, 2016 1 commit
    • Allow Member.add_user to handle access requesters · ec0061a9
      Rémy Coutable authored
      Changes include:
      
      - Ensure Member.add_user is not called directly when not necessary
      - New GroupMember.add_users_to_group to have the same abstraction level as for Project
      - Refactor Member.add_user to take a source instead of an array of members
      - Fix Rubocop offenses
      - Always use Project#add_user instead of project.team.add_user
      - Factorize users addition as members in Member.add_users_to_source
      - Make access_level a keyword argument in GroupMember.add_users_to_group and ProjectMember.add_users_to_projects
      - Destroy any requester before adding them as a member
      - Improve the way we handle access requesters in Member.add_user
        Instead of removing the requester and creating a new member,
        we now simply accepts their access request. This way, they will
        receive a "access request granted" email.
      - Fix error that was previously silently ignored
      - Stop raising when access level is invalid in Member, let Rails validation do their work
      Signed-off-by: 's avatarRémy Coutable <remy@rymai.me>
  34. 29 Jul, 2016 1 commit
    • Method for returning issues readable by a user · 002ad215
      Yorick Peterse authored
      The method Ability.issues_readable_by_user takes a list of users and an
      optional user and returns an Array of issues readable by said user. This
      method in turn is used by
      Banzai::ReferenceParser::IssueParser#nodes_visible_to_user so this
      method no longer needs to get all the available abilities just to check
      if a user has the "read_issue" ability.
      
      To test this I benchmarked an issue with 222 comments on my development
      environment. Using these changes the time spent in nodes_visible_to_user
      was reduced from around 120 ms to around 40 ms.