We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It looks like the intent on https://github.com/puma/puma/blob/master/lib/puma/cli.rb#L173 is to allow specifying -t <max> to mean 0:<max>.
-t <max>
0:<max>
But if that's the case, then it should be c.threads 0, min instead, since max is nil.
c.threads 0, min
max
nil
The text was updated successfully, but these errors were encountered:
4172f42
Thanks!
Sorry, something went wrong.
Use different Puma thread format to work around old Puma bug: puma/pu…
5cdc78a
…ma#984
No branches or pull requests
It looks like the intent on https://github.com/puma/puma/blob/master/lib/puma/cli.rb#L173 is to allow specifying
-t <max>
to mean0:<max>
.But if that's the case, then it should be
c.threads 0, min
instead, sincemax
isnil
.The text was updated successfully, but these errors were encountered: