gitlab-org--gitlab-foss/db/fixtures/development/02_application_settings.rb

# frozen_string_literal: true

puts "Creating the default ApplicationSetting record.".color(:green)
ApplicationSetting.create_from_defaults

# Details https://gitlab.com/gitlab-org/gitlab-foss/issues/46241
puts "Enable hashed storage for every new projects.".color(:green)
ApplicationSetting.current_without_cache.update!(hashed_storage_enabled: true)

print '.'
Fix race cond. in ApplicationSettingImplementation.create_from_defaults Signed-off-by: Rémy Coutable <remy@rymai.me> 2019-03-18 13:32:26 +00:00			`# frozen_string_literal: true`

			`puts "Creating the default ApplicationSetting record.".color(:green)`
Fix ApplicationSetting 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> 2019-04-10 10:03:37 +00:00			`ApplicationSetting.create_from_defaults`
Fix race cond. in ApplicationSettingImplementation.create_from_defaults Signed-off-by: Rémy Coutable <remy@rymai.me> 2019-03-18 13:32:26 +00:00
Add latest changes from gitlab-org/gitlab@master 2019-09-18 14:02:45 +00:00			`# Details https://gitlab.com/gitlab-org/gitlab-foss/issues/46241`
Fix race cond. in ApplicationSettingImplementation.create_from_defaults Signed-off-by: Rémy Coutable <remy@rymai.me> 2019-03-18 13:32:26 +00:00			`puts "Enable hashed storage for every new projects.".color(:green)`
			`ApplicationSetting.current_without_cache.update!(hashed_storage_enabled: true)`

			`print '.'`