Puma 3.8.2 ignoring configuration and environment

[martinobettucci]

I fixed going back to 3.6.2

Steps to reproduce

printenv

SHELL=/bin/bash
RACK_ENV=production
WEB_CONCURRENCY=3
LANG=en_GB.UTF-8
rvm_ruby_string=ruby-2.4.0
MAX_THREADS=5
PORT=9282
RUBY_VERSION=ruby-2.4.0
_=/usr/bin/printenv

Puma startup command was
pumactl start

Expected behavior

Startup log of 3.6.2 The correct working one

[26055] Puma starting in cluster mode...
[26055] * Version 3.6.2 (ruby 2.4.0-p0), codename: Sleepy Sunday Serenity
[26055] * Min threads: 5, max threads: 5
[26055] * Environment: production
[26055] * Process workers: 3
[26055] * Preloading application
[26055] * Listening on tcp://0.0.0.0:9282
[26055] ! WARNING: Detected 1 Thread(s) started in app boot:
[26055] ! #<Thread:0x00000002bc1360@/home/martino/.rvm/gems/ruby-2.4.0@nss-groupsend-fe/gems/rufus-scheduler-3.4.0/lib/rufus/scheduler.rb:546 sleep> - /home/martino/.rvm/gems/ruby-2.4.0@nss-groupsend-fe/gems/rufus-scheduler-3.4.0/lib/rufus/scheduler.rb:554:in `sleep'
[26055] * Daemonizing...

Actual behavior

Startup log of 3.8.2 The actual wrong one

Puma starting in single mode...
* Version 3.8.2 (ruby 2.4.0-p0), codename: Sassy Salamander
* Min threads: 0, max threads: 16
* Environment: production
* Listening on tcp://0.0.0.0:9292
Use Ctrl-C to stop
^C- Gracefully stopping, waiting for requests to finish
=== puma shutdown: 2017-05-04 10:47:27 +0200 ===
- Goodbye!

System configuration

Ruby version: 2.4.0
Rails version: 5.0.1

[ccarruitero]

I think it is already fixed in master with #1277