Name |
Last commit
|
Last update |
---|---|---|
.. | ||
blob | ||
commit | ||
commits | ||
diffs | ||
environments | ||
imports | ||
issues | ||
jobs | ||
merge_requests | ||
notes | ||
pipelines | ||
registry/repositories | ||
tags | ||
tree | ||
_home_panel.html.haml_spec.rb | ||
edit.html.haml_spec.rb |
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 |
---|---|---|
.. | ||
blob | Loading commit data... | |
commit | Loading commit data... | |
commits | Loading commit data... | |
diffs | Loading commit data... | |
environments | Loading commit data... | |
imports | Loading commit data... | |
issues | Loading commit data... | |
jobs | Loading commit data... | |
merge_requests | Loading commit data... | |
notes | Loading commit data... | |
pipelines | Loading commit data... | |
registry/repositories | Loading commit data... | |
tags | Loading commit data... | |
tree | Loading commit data... | |
_home_panel.html.haml_spec.rb | Loading commit data... | |
edit.html.haml_spec.rb | Loading commit data... |