An error occurred fetching the project authors.
  1. 30 Jul, 2018 1 commit
  2. 16 May, 2018 1 commit
  3. 05 Apr, 2018 1 commit
  4. 05 Mar, 2018 1 commit
  5. 03 Mar, 2018 1 commit
  6. 22 Feb, 2018 1 commit
  7. 01 Feb, 2018 1 commit
    • Yorick Peterse's avatar
      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.
      cca61980
  8. 20 Nov, 2017 1 commit
  9. 06 Oct, 2017 1 commit
    • Toon Claes's avatar
      Create idea of read-only database · d1366971
      Toon Claes authored
      In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
      secondary node). But in GitLab CE it also might be useful to have the
      "read-only" idea around. So port it back to GitLab CE.
      
      Also having the principle of read-only in GitLab CE would hopefully
      lead to less errors introduced, doing write operations when there
      aren't allowed for read-only calls.
      
      Closes gitlab-org/gitlab-ce#37534.
      d1366971
  10. 12 Sep, 2017 2 commits
  11. 06 Sep, 2017 1 commit
  12. 31 Aug, 2017 2 commits
  13. 28 Aug, 2017 1 commit