-
-
Notifications
You must be signed in to change notification settings - Fork 233
Block reload config files in Railtie if they already uploaded #353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
6a02452
to
b43c196
Compare
It affects tests which execute `rails runner`
d25a628
to
5db7fc4
Compare
@cjlarose, could you check tests? |
@vovanmozg are you still interested in moving forward with this PR? |
@Nuzair46 what do you think about this one? |
|
||
```ruby | ||
Config.setup do |config| | ||
config.load_and_set_settings("/path/to/yaml1", "/path/to/yaml2", ...) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this comment suggests in the original issue #352 (comment)
I think its better to be
Config.setup { ... }
Config.load_and_set_settings("...")
Because it feels more right.
@pkuczynski @vovanmozg the failing tests seems to be an issue with Rails 6.1 not loading logger properly. `#{Rails.root.join("bin", "rails")} runner 'print "\#{Settings.default}|\#{Settings.custom}"'` After: `RUBYOPT="-r logger" #{Rails.root.join("bin", "rails")} runner 'print "\#{Settings.default}|\#{Settings.custom}"'` This makes ruby to load the logger before anything runs. |
Fixes #352