Errno::EBADF: Bad file descriptor - not a socket file descriptor in Puma. about puma-dev HOT 4 CLOSED

I get the same thing with Puma 3.4.0 and Ruby 2.3.1-p112.

$ ./bin/puma-dev
[snip]
foo[70138]: * Version 3.4.0 (ruby 2.3.1-p112), codename: Owl Bowl Brawl
[snip]
bundler: failed to load command: puma (/Users/bill/.rbenv/versions/2.3.1/bin/puma)

Running the puma command manually does work (it complains about no configured application, as expected).

$ /Users/bill/.rbenv/versions/2.3.1/bin/puma
Puma starting in single mode...
* Version 3.4.0 (ruby 2.3.1-p112), codename: Owl Bowl Brawl
* Min threads: 0, max threads: 16
* Environment: development
ERROR: No application configured, nothing to run

from puma-dev.

The no app configured message is because when you run it manually it is likely looking in a different directory for the app files.

from puma-dev.

@billhorsman can you gist the entire output without snips? That context doesn't tell much of a picture.

from puma-dev.

Here is the full context for me when I get this error: https://gist.github.com/BJClark/4884bc5497c94d18dec230d9af87cc88

Fwiw, I can run regular puma on this app just fine, that's what I use every day.

from puma-dev.