diff options
| author | Rémy Coutable <remy@rymai.me> | 2019-04-10 12:03:37 +0200 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2019-04-10 15:56:46 +0200 |
| commit | 22c1c9805b00ebc3bbb48fabba49cf2ba3e696e0 (patch) | |
| tree | 642b04ecba8c0880ae8b36c99c95280ac9ff011f /db/fixtures | |
| parent | 6c8a13da33e5ff11210122f7863d36f989b99630 (diff) | |
| download | gitlab-ce-22c1c9805b00ebc3bbb48fabba49cf2ba3e696e0.tar.gz | |
Fix ApplicationSetting development seed60278-fix-development-seed
It could happen that there's a cached (in Redis) ApplicationSetting
record, and calling
`Gitlab::CurrentSettings.current_application_settings` only returns it
instead of creating a new DB record, which makes the
`ApplicationSetting.current_without_cache.update!` call fail.
Signed-off-by: Rémy Coutable <remy@rymai.me>
Diffstat (limited to 'db/fixtures')
| -rw-r--r-- | db/fixtures/development/02_application_settings.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/db/fixtures/development/02_application_settings.rb b/db/fixtures/development/02_application_settings.rb index d604f0be3cd..7cdc8e40b69 100644 --- a/db/fixtures/development/02_application_settings.rb +++ b/db/fixtures/development/02_application_settings.rb @@ -1,7 +1,7 @@ # frozen_string_literal: true puts "Creating the default ApplicationSetting record.".color(:green) -Gitlab::CurrentSettings.current_application_settings +ApplicationSetting.create_from_defaults # Details https://gitlab.com/gitlab-org/gitlab-ce/issues/46241 puts "Enable hashed storage for every new projects.".color(:green) |