An error occurred fetching the project authors.
- 30 Jul, 2018 1 commit
-
-
Felipe Artur authored
-
- 16 May, 2018 1 commit
-
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 05 Apr, 2018 1 commit
-
-
Felipe Artur authored
-
- 05 Mar, 2018 1 commit
-
-
Felipe Artur authored
-
- 03 Mar, 2018 1 commit
-
-
Felipe Artur authored
-
- 22 Feb, 2018 1 commit
-
-
Bob Van Landuyt authored
-
- 01 Feb, 2018 1 commit
-
-
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.
-
- 20 Nov, 2017 1 commit
-
-
Oswaldo Ferreira authored
-
- 06 Oct, 2017 1 commit
-
-
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.
-
- 12 Sep, 2017 2 commits
-
-
micael.bergeron authored
added a QueryRecorder for IssuesController#index.json
-
micael.bergeron authored
-
- 06 Sep, 2017 1 commit
-
-
Felipe Artur authored
-
- 31 Aug, 2017 2 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
- 28 Aug, 2017 1 commit
-
-
Felipe Artur authored
-