diff options
author | schneems <richard.schneeman@gmail.com> | 2016-06-06 11:26:22 -0500 |
---|---|---|
committer | schneems <richard.schneeman@gmail.com> | 2016-06-06 11:34:32 -0500 |
commit | 7bd41994480c17db71fdc07e3447ade929eaa386 (patch) | |
tree | 1a371428ed303eea71d9d1f991810359e545d60e /activesupport/test/multibyte_conformance_test.rb | |
parent | 3fc5577363dc4049cd1d0bba8f3fa9296f1ced57 (diff) | |
download | rails-7bd41994480c17db71fdc07e3447ade929eaa386.tar.gz rails-7bd41994480c17db71fdc07e3447ade929eaa386.tar.bz2 rails-7bd41994480c17db71fdc07e3447ade929eaa386.zip |
EventedFileUpdateChecker boots once per process
We need one file checker booted per process as talked about in #24990. Before we do a check to see if any updates have been registered by the listener we first check to make sure that the current process has booted a listener.
We are intentionally not starting a listener when the checker is created. This way we can avoid #25259 in which puma warns of multiple threads created before fork. As written the listener for each process will be invoked by the `ActionDispatch::Executor` middleware when the `updated?` method is called. This is the first middleware on the stack and will be invoked before application code is read into memory.
The downside of this approach is that the API is a little less obvious. I.e. that you have to call `updated?` to get the listener to start is not intuitive. We could make `boot!` not private if we want to make the API a little nicer. Alternatively we could boot when the checker is initialized however this reintroduces the puma threads warning, and also means that in cases of `rails server` or when using `preload!` that we have extra threads notifying of changes on a process that we don't care about.
[close #24990] [close #25259]
Diffstat (limited to 'activesupport/test/multibyte_conformance_test.rb')
0 files changed, 0 insertions, 0 deletions