Skip to content
New issue

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

Fix warn_if_in_single_mode incorrect message #3111

Merged
merged 1 commit into from Mar 30, 2023
Merged

Conversation

adzap
Copy link
Contributor

@adzap adzap commented Mar 29, 2023

Description

The message about hooks when in single mode is worded incorrectly. The message could either be in the positive but Puma is configured to run in single mode (worker count = 0 ) or the negative but Puma is not configured to run in cluster mode (worker count > 0 ). I went with negative because it explicitly instructs what is required in order for hooks to run.

Your checklist for this pull request

  • I have reviewed the guidelines for contributing to this repository.
  • I have added (or updated) appropriate tests if this PR fixes a bug or adds a feature.
  • My pull request is 100 lines added/removed or less so that it can be easily reviewed.
  • If this PR doesn't need tests (docs change), I added [ci skip] to the title of the PR.
  • If this closes any issues, I have added "Closes #issue" to the PR description or my commit messages.
  • I have updated the documentation accordingly.
  • All new and existing tests passed, including Rubocop.

The message could either be in the positive `but Puma is configured to run in single mode (worker count = 0 )` or the negative `but Puma is not configured to run in cluster mode (worker count > 0 )`. I went with negative because it explicitly instructs what is required in order for hooks to run.
@nateberkopec
Copy link
Member

Whoops 😅

@nateberkopec nateberkopec merged commit 52fa8f6 into puma:master Mar 30, 2023
64 of 65 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants