BigW Consortium Gitlab

  1. 01 Feb, 2018 1 commit
    • Track and act upon the number of executed queries · cca61980
      Yorick Peterse authored
      This ensures that we have more visibility in the number of SQL queries
      that are executed in web requests. The current threshold is hardcoded to
      100 as we will rarely (maybe once or twice) change it.
      
      In production and development we use Sentry if enabled, in the test
      environment we raise an error. This feature is also only enabled in
      production/staging when running on GitLab.com as it's not very useful to
      other users.
  2. 31 Jan, 2018 2 commits
  3. 23 Jan, 2018 1 commit
    • Use limit for search count queries · 090ca9c3
      Jan Provaznik authored
      Search query is especially slow if a user searches a generic string
      which matches many records, in such case search can take tens of
      seconds or time out. To speed up the search query, we search only for
      first 1000 records, if there is >1000 matching records we just display
      "1000+" instead of precise total count supposing that with such amount
      the exact count is not so important for the user.
      
      Because for issues even limited search was not fast enough, 2-phase
      approach is used for issues: first we use simpler/faster query to get
      all public issues, if this exceeds the limit, we just return the limit.
      If the amount of matching results is lower than limit, we re-run more
      complex search query (which includes also confidential issues).
      Re-running the complex query should be fast enough in such case because the
      amount of matching issues is lower than limit.
      
      Because exact total_count is now limited, this patch also switches to
      to "prev/next" pagination.
      
      Related #40540
  4. 21 Jan, 2018 1 commit
  5. 17 Jan, 2018 2 commits
    • Merge branch 'sh-migrate-can-push-to-deploy-keys-projects-10-3' into 'security-10-3' · 536a47b4
      Douwe Maan authored
      [10.3] Migrate `can_push` column from `keys` to `deploy_keys_project`
      
      See merge request gitlab/gitlabhq!2276
      
      (cherry picked from commit f6ca52d31bac350a23938e0aebf717c767b4710c)
      
      1f2bd3c0 Backport to 10.3
    • Merge branch… · 0424801e
      Stan Hu authored
      Merge branch 'security-10-3-do-not-expose-passwords-or-tokens-in-service-integrations-api' into 'security-10-3'
      
      Filter out sensitive fields from the project services API
      
      See merge request gitlab/gitlabhq!2281
      
      (cherry picked from commit 476f2576444632f2a9a61b4cead9c1077f2c81d7)
      
      2bcbbda0 Filter out sensitive fields from the project services API
  6. 15 Jan, 2018 1 commit
  7. 14 Jan, 2018 1 commit
  8. 13 Jan, 2018 1 commit
    • Fix N+1 in v3 builds API · c9a1a155
      Matija Čupić authored
      The N+1 issue was caused by loading the job_artifacts_archive for each
      job (build) individually. Including that in the builds
      AssociationRelation fixed the issue.
  9. 11 Jan, 2018 1 commit
  10. 09 Jan, 2018 1 commit
  11. 08 Jan, 2018 1 commit
  12. 04 Jan, 2018 1 commit
  13. 19 Dec, 2017 1 commit
    • Only include the user's ID in the time_spent command's update hash · 3e4b45fc
      Robert Speicher authored
      Previously, this would include the entire User record in the update
      hash, which was rendered in the response using `to_json`, erroneously
      exposing every attribute of that record, including their (now removed)
      private token.
      
      Now we only include the user ID, and perform the lookup on-demand.
  14. 23 Nov, 2017 1 commit
  15. 16 Nov, 2017 1 commit
  16. 08 Nov, 2017 1 commit
  17. 06 Nov, 2017 4 commits
  18. 13 Oct, 2017 4 commits
  19. 12 Oct, 2017 1 commit
  20. 05 Oct, 2017 1 commit
  21. 07 Sep, 2017 1 commit
  22. 06 Sep, 2017 3 commits
  23. 04 Sep, 2017 5 commits
  24. 16 Aug, 2017 1 commit
  25. 14 Aug, 2017 2 commits