You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When run without -d option application error is logged to stderr.
$ puma -C puma-config.rb
Puma 2.1.0 starting...
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://0.0.0.0:9292
config.ru:4:in `block in <main>': undefined local variable or method `problem' for #<Rack::Builder:0xa22c6f8 @map=nil, @run=nil, @use=[]> (NameError)
When run with -d option the application error is lost, neither written to stderr nor to the file specified in stdout_redirect.
In my opinion it should always log the application load errors to the file if stdout_redirect was specified.
Minimal example:
When run without
-d
option application error is logged to stderr.When run with
-d
option the application error is lost, neither written to stderr nor to the file specified instdout_redirect
.In my opinion it should always log the application load errors to the file if
stdout_redirect
was specified.Confirmed on current master.
Was mentioned in #253 (comment) by @sabcio.
I will come up with a pull request for this in the next few days.
The text was updated successfully, but these errors were encountered: