BigW Consortium Gitlab
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.
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
ci | Loading commit data... | |
gitlab | Loading commit data... | |
migrate | Loading commit data... | |
brakeman.rake | Loading commit data... | |
cache.rake | Loading commit data... | |
config_lint.rake | Loading commit data... | |
dev.rake | Loading commit data... | |
downtime_check.rake | Loading commit data... | |
ee_compat_check.rake | Loading commit data... | |
eslint.rake | Loading commit data... | |
flay.rake | Loading commit data... | |
gemojione.rake | Loading commit data... | |
gettext.rake | Loading commit data... | |
grape.rake | Loading commit data... | |
haml-lint.rake | Loading commit data... | |
import.rake | Loading commit data... | |
karma.rake | Loading commit data... | |
lint.rake | Loading commit data... | |
rubocop.rake | Loading commit data... | |
scss-lint.rake | Loading commit data... | |
services.rake | Loading commit data... | |
setup.rake | Loading commit data... | |
sidekiq.rake | Loading commit data... | |
spec.rake | Loading commit data... | |
spinach.rake | Loading commit data... | |
test.rake | Loading commit data... | |
tokens.rake | Loading commit data... | |
yarn.rake | Loading commit data... |