Actions
Patch #37867
closedLimit puma < 6.0.0 to avoid system test error
Description
Recently, system test fails with the following error.
% bundle exec rails test:system
Run options: --seed 40281
# Running:
#<Thread:0x000000011134ded0 /Users/sanak/Build/rb/redmine/vendor/bundle/ruby/3.1.0/gems/capybara-3.36.0/lib/capybara/server.rb:76 run> terminated with exception (report_on_exception is true):
/Users/sanak/Build/rb/redmine/vendor/bundle/ruby/3.1.0/gems/capybara-3.36.0/lib/capybara/registrations/servers.rb:32:in `block in <top (required)>': undefined method `stdio' for Puma::Events:Class (NoMethodError)
events = conf.options[:Silent] ? ::Puma::Events.strings : ::Puma::Events.stdio
^^^^^^
from /Users/sanak/Build/rb/redmine/vendor/bundle/ruby/3.1.0/gems/capybara-3.36.0/lib/capybara/config.rb:64:in `block in server='
from /Users/sanak/Build/rb/redmine/vendor/bundle/ruby/3.1.0/gems/capybara-3.36.0/lib/capybara/server.rb:77:in `block in boot'
From the following links,
- Slack link: https://stackoverflow.com/questions/74160636/nomethoderror-undefined-method-strings-for-pumaeventsclass
- GitHub link: https://github.com/teamcapybara/capybara/issues/2598
limiting puma < 6.0.0 seems to be better, because capybara version is specified in Gemfile.
I upload a simple patch to limit puma < 6.0.0, so reviewing it is helpful.
Files
Related issues
Actions