BigW Consortium Gitlab

  1. 06 Apr, 2017 1 commit
    • ProjectsFinder should handle more options · b996a82f
      Jacopo authored
      Extended ProjectFinder in order to handle the following options:
       - current_user - which user use
       - project_ids_relation: int[] - project ids to use
       - params:
         -  trending: boolean
         -  non_public: boolean
         -  starred: boolean
         -  sort: string
         -  visibility_level: int
         -  tags: string[]
         -  personal: boolean
         -  search: string
         -  non_archived: boolean
      
      GroupProjectsFinder now inherits from ProjectsFinder.
      Changed the code in order to use the new available options.
  2. 24 Mar, 2017 1 commit
    • Refactored the user callout class · 3eedb2ae
      Phil Hughes authored
      Instead of the JS being in charge of the HTML, the HAML now handles it.
      The HAML can then check the cookie & show it needed. It also allows the
      HAML access to the paths so we don't have to pass that through.
      
      Closes #29955
  3. 09 Mar, 2017 1 commit
  4. 03 Mar, 2017 2 commits
  5. 28 Feb, 2017 1 commit
  6. 23 Feb, 2017 4 commits
  7. 31 Dec, 2016 1 commit
  8. 29 Nov, 2016 1 commit
  9. 15 Jul, 2016 1 commit
  10. 08 Jul, 2016 1 commit
  11. 03 Jun, 2016 2 commits
  12. 23 May, 2016 1 commit
  13. 14 Mar, 2016 1 commit
  14. 13 Mar, 2016 1 commit
  15. 03 Mar, 2016 1 commit
    • Refactor projects list · 7455d950
      Dmitriy Zaporozhets authored
      1. Fix double bottom border if pagination
      2. Fix broken search on forks page
      4. Remove duplicate js logic
      4. Remove unused show all link
      5. Remove duplicate “no project” message in different views
      
      After this merge request you can easily render shared projects template
      with all necessary html/js included to make searchable list with
      pagination. All you need to provide is controller that returns
      projects list with seach nad pagination and render html form with
      project-filter-form id and text field with filter_projects name.
      Signed-off-by: 's avatarDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
  16. 02 Mar, 2016 1 commit
  17. 19 Feb, 2016 1 commit
  18. 04 Feb, 2016 3 commits
  19. 27 Jan, 2016 1 commit
    • Use Atom update times of the first event · de7c9c7a
      Yorick Peterse authored
      By simply loading the first event from the already sorted set we save
      ourselves extra (slow) queries just to get the latest update timestamp.
      This removes the need for Event.latest_update_time and significantly
      reduces the time needed to build an Atom feed.
      
      Fixes gitlab-org/gitlab-ce#12415
  20. 08 Jan, 2016 2 commits
  21. 23 Dec, 2015 1 commit
  22. 21 Dec, 2015 1 commit
  23. 03 Dec, 2015 1 commit
  24. 18 Nov, 2015 1 commit
    • Faster way of obtaining latest event update time · 054f2f98
      Yorick Peterse authored
      Instead of using MAX(events.updated_at) we can simply sort the events in
      descending order by the "id" column and grab the first row. In other
      words, instead of this:
      
          SELECT max(events.updated_at) AS max_id
          FROM events
          LEFT OUTER JOIN projects   ON projects.id   = events.project_id
          LEFT OUTER JOIN namespaces ON namespaces.id = projects.namespace_id
          WHERE events.author_id IS NOT NULL
          AND events.project_id IN (13083);
      
      we can use this:
      
          SELECT events.updated_at AS max_id
          FROM events
          LEFT OUTER JOIN projects   ON projects.id   = events.project_id
          LEFT OUTER JOIN namespaces ON namespaces.id = projects.namespace_id
          WHERE events.author_id IS NOT NULL
          AND events.project_id IN (13083)
          ORDER BY events.id DESC
          LIMIT 1;
      
      This has the benefit that on PostgreSQL a backwards index scan can be
      used, which due to the "LIMIT 1" will at most process only a single row.
      This in turn greatly speeds up the process of grabbing the latest update
      time. This can be confirmed by looking at the query plans. The first
      query produces the following plan:
      
          Aggregate  (cost=43779.84..43779.85 rows=1 width=12) (actual time=2142.462..2142.462 rows=1 loops=1)
            ->  Index Scan using index_events_on_project_id on events  (cost=0.43..43704.69 rows=30060 width=12) (actual time=0.033..2138.086 rows=32769 loops=1)
                  Index Cond: (project_id = 13083)
                  Filter: (author_id IS NOT NULL)
          Planning time: 1.248 ms
          Execution time: 2142.548 ms
      
      The second query in turn produces the following plan:
      
          Limit  (cost=0.43..41.65 rows=1 width=16) (actual time=1.394..1.394 rows=1 loops=1)
            ->  Index Scan Backward using events_pkey on events  (cost=0.43..1238907.96 rows=30060 width=16) (actual time=1.394..1.394 rows=1 loops=1)
                  Filter: ((author_id IS NOT NULL) AND (project_id = 13083))
                  Rows Removed by Filter: 2104
          Planning time: 0.166 ms
          Execution time: 1.408 ms
      
      According to the above plans the 2nd query is around 1500 times faster.
      However, re-running the first query produces timings of around 80 ms,
      making the 2nd query "only" around 55 times faster.
  25. 12 Oct, 2015 2 commits
  26. 10 Oct, 2015 1 commit
  27. 01 Oct, 2015 1 commit
  28. 25 Sep, 2015 1 commit
    • Project page Update · 12acf15c
      Andrey authored
      refactoring buttons, fixes for projects filter on the dashboard and
      group page
  29. 24 Sep, 2015 1 commit
  30. 08 Sep, 2015 2 commits