- 12 May, 2017 3 commits
-
-
Douwe Maan authored
-
Valery Sizov authored
-
Phil Hughes authored
-
- 11 May, 2017 8 commits
-
-
Pawel Chojnacki authored
+ fix tests
-
Pawel Chojnacki authored
- Tests for prometheus queries - fix rubocop warnings - Remove unused method. Add more queries to deployment queries. - Wrap BaseQuery in module hierarchy Renname Prometheus class to PrometheusClient
-
Douwe Maan authored
-
Jarka Kadlecova authored
-
Jacob Vosmaer authored
-
Z.J. van de Weg authored
Enforced by the database, and no callbacks need to be called. Combined with 7b9b2c6099 and 294a8b8a6d this resolves gitlab-org/gitlab-ce#31799
-
Douwe Maan authored
-
Douwe Maan authored
-
- 10 May, 2017 6 commits
-
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Phil Hughes authored
Closes #31541
-
Douwe Maan authored
Refactor snippets finder & dont return internal snippets for external users See merge request !2094
-
Douwe Maan authored
-
blackst0ne authored
-
- 09 May, 2017 7 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Toon Claes authored
In commit 020295ff a regex was added to quickly determine if mentionables might be referenced. But this didn't take into account the note might not belong to a project. So when it doesn't belong to a project, assume the default issue tracker is used, and use DEFAULT_PATTERN to check if there are mentionables. Fixes gitlab-org/gitlab-ce#31993
-
Fatih Acet authored
-
- 08 May, 2017 7 commits
-
-
Felipe Artur authored
-
Felipe Artur authored
-
Felipe Artur authored
-
Toon Claes authored
Not assigning the trackable fields seems to cause strange side-effects.
-
Toon Claes authored
Every time a user logs in or out, the Trackable attributes are written to the database. This is causing a lot of load on the database, for data that isn't really critical. So to avoid the database being hammered, add a Gitlab::ExclusiveLease before writing trackable attributes to the database. This lease expires after an hour, so only when the attributes were written more than an hour ago, they can be written again. Otherwise they are ignored.
-
Chris Wilson authored
The notify_only_default_branch property is using boolean_accessor this means we need to check it using a question methods. Also add specs for disabling this option.
-
Stan Hu authored
On databases such as MySQL, it's possible to get into a timing comparison error if the value of `Confirmable#confirmation_sent_at` is within a second of `0.days.ago`. This is possible mostly in specs that test this behavior and most likely not happening in practice. The result of this error causes a user to be deemed active when it should be inactive. To prevent this error, we explicitly check the configuration setting to be `0.days.ago`. Closes gitlab-org/gitlab-ee#2362
-
- 07 May, 2017 3 commits
-
-
Zeger-Jan van de Weg authored
-
Ahmad Sherif authored
-
Kamil Trzcinski authored
-
- 06 May, 2017 2 commits
-
-
Zeger-Jan van de Weg authored
-
Sean McGivern authored
-
- 05 May, 2017 4 commits
-
-
Michael Kozono authored
We’ve seen a deadlock in CI here https://gitlab.com/mkozono/gitlab-ce/builds/15644492#down-build-trace. This commit should not fix that particular failure, but perhaps it will avoid others. * Don’t call delete_conflicting_redirects after update if the path wasn’t changed * Rename descendants without using recursion again, so we can run delete_conflicting_redirects exactly once.
-
Michael Kozono authored
-
Michael Kozono authored
-
Michael Kozono authored
-