"Detected 1 Thread(s) started in app boot" on puma 3.4.0 about puma_worker_killer HOT 5 CLOSED

No, that warning can be safely ignored. I don't know of a better way to initialize this code.

-- 
Richard Schneeman
http://schneems.com

On May 4, 2016 at 4:19:21 PM, Diego Algorta ([email protected]) wrote:

Recently upgraded from Puma 2.15.3 to 3.4.0 and puma_worker_killer 0.0.4 to 0.0.6. I'm also using puma-heroku 1.0.0 plugin as the config I had was basically the same as that plugin's.

from puma_worker_killer.

Ok, thanks. Maybe @evanphx does, considering it's related to an upgrade to Puma 3?

from puma_worker_killer.

You're talking about this right?

2016-05-04T20:56:29.887162+00:00 app[web.1]: [3] ! WARNING: Detected 1 Thread(s) started in app boot:
2016-05-04T20:56:29.887296+00:00 app[web.1]: [3] ! #<Thread:0x007f40c3d331e0@/app/vendor/bundle/ruby/2.2.0/gems/puma_worker_killer-0.0.6/lib/puma_worker_killer/auto_reap.rb:12 sleep> - /app/vendor/bundle/ruby/2.2.0/gems/puma_worker_killer-0.0.6/lib/puma_worker_killer/auto_reap.rb:15:in `sleep'
2016-05-04T20:56:29.887677+00:00 app[web.1]: [3] Use Ctrl-C to stop

Puma has been warning about threads at start up for a number of versions. I don't know when they were introduced though.

from puma_worker_killer.

The warning is just that, a warning. If the code can deal with that thread not living into the workers, then it's fine. Puma doesn't know which are master threads and which are worker threads, so it just makes as much info available as possible.

from puma_worker_killer.

Ok then... I'll just ignore it. Thanks!

from puma_worker_killer.