e7d743b8ac
When the webdrivers gem is not present (which is the default scenario in Rails 7.1+), the Selenium `driver_path` starts out as `nil`. This means the driver is located lazily, and deferred until a system test is run. If parallel testing is used, this leads to a race condition, where each worker process tries to resolve the driver simultaneously. The result is an error as described in #49906. This commit fixes the race condition by changing the implementation of `Browser#preload`. The previous implementation worked when `driver_path` was set to a Proc by the `webdrivers` gem, but doesn't work when the `webdrivers` gem is not being used and the `driver_path` is `nil`. `Browser#preload` now uses the `DriverFinder` utility provided by the `selenium-webdriver` gem to eagerly resolve the driver path if needed. This will ensures that `driver_path` is set before parallel test workers are forked. Fixes #49906. Co-authored-by: Jonathan Hefner <jonathan@hefner.pro> |
||
---|---|---|
.. | ||
bin | ||
lib | ||
test | ||
actionpack.gemspec | ||
CHANGELOG.md | ||
MIT-LICENSE | ||
Rakefile | ||
README.rdoc |
= Action Pack -- From request to response Action Pack is a framework for handling and responding to web requests. It provides mechanisms for *routing* (mapping request URLs to actions), defining *controllers* that implement actions, and generating responses. In short, Action Pack provides the controller layer in the MVC paradigm. It consists of several modules: * Action Dispatch, which parses information about the web request, handles routing as defined by the user, and does advanced processing related to HTTP such as MIME-type negotiation, decoding parameters in POST, PATCH, or PUT bodies, handling HTTP caching logic, cookies and sessions. * Action Controller, which provides a base controller class that can be subclassed to implement filters and actions to handle requests. The result of an action is typically content generated from views. With the Ruby on \Rails framework, users only directly interface with the Action Controller module. Necessary Action Dispatch functionality is activated by default and Action View rendering is implicitly triggered by Action Controller. However, these modules are designed to function on their own and can be used outside of \Rails. You can read more about Action Pack in the {Action Controller Overview}[https://guides.rubyonrails.org/action_controller_overview.html] guide. == Download and installation The latest version of Action Pack can be installed with RubyGems: $ gem install actionpack Source code can be downloaded as part of the \Rails project on GitHub: * https://github.com/rails/rails/tree/main/actionpack == License Action Pack is released under the MIT license: * https://opensource.org/licenses/MIT == Support API documentation is at: * https://api.rubyonrails.org Bug reports for the Ruby on \Rails project can be filed here: * https://github.com/rails/rails/issues Feature requests should be discussed on the rails-core mailing list here: * https://discuss.rubyonrails.org/c/rubyonrails-core