-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Removal of Puma::Server#min_threads=
breaks Capybara
#2388
Labels
Comments
Thanks for reporting. This was a mistake. I'll revert and release 5.0.2. |
kevindew
added a commit
to alphagov/govuk_publishing_components
that referenced
this issue
Sep 28, 2020
Puma 5.0.1 was released an hour ago and introduces an API incompatibility with Capybara [1], which causes the tests to fail for this project in CI. This applies a quick fix to get these tests working again while the Puma situation is resolved. Should this be more than a simple mistake we'll need to re-release govuk_test to cater for it. [1]: puma/puma#2388
kevindew
added a commit
to alphagov/govuk_publishing_components
that referenced
this issue
Sep 28, 2020
Puma 5.0.1 was released an hour ago and introduces an API incompatibility with Capybara [1], which causes the tests to fail for this project in CI. As this project is a Gem the contents of the Gemfile.lock are not used to install the gem on CI [2] which means new versions of dependencies can break builds without us intervening. This applies a quick fix to get these tests working again while the Puma situation is resolved. Should this be more than a simple mistake we'll need to re-release govuk_test to cater for it. [1]: puma/puma#2388 [2]: https://github.com/alphagov/govuk-jenkinslib/blob/cdd76bbc0fb59e7a13ecc9dd9e6bb4518d6dfc97/vars/govuk.groovy#L654
Fixed in 5.0.2 |
7 tasks
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
With Puma 5.0.0, the latest Capybara properly boots my Rails test server.
With Puma 5.0.1, it gives an error.
I know this is technically a Capybara issue, but I wanted to let you know since it is a breaking change to Puma's API between 5.0.0 and 5.0.1 and wanted to see if that was expected.
See teamcapybara/capybara#2397
Puma config:
See https://github.com/teamcapybara/capybara/blob/952c4c21e70ba8fcea6de469ae7d555c279cebf5/lib/capybara/registrations/servers.rb#L42
To Reproduce
Expected behavior
It should properly boot.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: