- 31 Aug, 2017 1 commit
-
-
Sean McGivern authored
The initializers including this were doing so at the top level, so every object loaded after them had a `current_application_settings` method. However, if someone had rack-attack enabled (which was loaded before these initializers), it would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't have that method. To fix this: 1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need `Object.new.current_application_settings` to work. 2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it like that in several places. 3. Change the initializers to use that new form.
-
- 30 Aug, 2017 1 commit
-
-
Hiroyuki Sato authored
-
- 29 Aug, 2017 1 commit
-
-
Robert Schilling authored
-
- 28 Aug, 2017 5 commits
-
-
James Lopez authored
-
Robert Schilling authored
-
James Lopez authored
-
Grzegorz Bizon authored
-
Simon Knox authored
-
- 24 Aug, 2017 1 commit
-
-
Robert Schilling authored
-
- 23 Aug, 2017 2 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 22 Aug, 2017 2 commits
-
-
Grzegorz Bizon authored
Since this already exists in `every_sidekiq_worker_spec.rb`.
-
Grzegorz Bizon authored
-
- 21 Aug, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 17 Aug, 2017 1 commit
-
-
Grzegorz Bizon authored
-
- 16 Aug, 2017 5 commits
-
-
Bob Van Landuyt authored
This allows testing every storage attempt after a failure. Which could be useful for tests
-
Clement Ho authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 15 Aug, 2017 2 commits
-
-
Robert Speicher authored
-
Winnie Hellmann authored
-
- 14 Aug, 2017 1 commit
-
-
Jacob Vosmaer authored
-
- 10 Aug, 2017 1 commit
-
-
Robert Speicher authored
-
- 09 Aug, 2017 4 commits
-
-
Simon Knox authored
-
Lin Jen-Shin authored
-
Bob Van Landuyt authored
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
- 08 Aug, 2017 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
If we set `ENCODING_CONFIDENCE_THRESHOLD` to 40, this test case would not pass. If we raise to 50, this would pass. Note that if in the future rugged didn't return corrupt data, this would be less relevant. But still icu recommend the threshold to be 50, we should just stick with 50.
-
- 07 Aug, 2017 5 commits
-
-
Jarka Kadlecova authored
-
Lin Jen-Shin authored
So that we could make sure migration tests could run even if geo is not setup in EE. This is because we have a model like this: ``` ruby class Geo::BaseRegistry < ActiveRecord::Base def self.connection raise 'Geo secondary database is not configured' unless Gitlab::Geo.geo_database_configured? super end end ```
-
Mehdi Lahmam authored
Currently, when a user wants to assign an issue/MR to himself, he needs to type his full username or select it from the suggested ones in the dropdown list. This commits suggest a faster solution which is typing `/assign me` Closes #35304.
-
Sean McGivern authored
-
Sean McGivern authored
Group milestones can only be referred to by name, not IID. They also do not support cross-project references.
-
- 04 Aug, 2017 5 commits
-
-
Rémy Coutable authored
Print the setup steps and duration and fix an issue resulting in re-setuping GitLab Shell on each test run Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
Signed-off-by: Rémy Coutable <remy@rymai.me>
-
Rémy Coutable authored
This reverts commit 23c502b4, reversing changes made to 1018ab05.
-
Bob Van Landuyt authored
-