NOTICE: Ending support for this gem about chromedriver-helper

[flavorjones]

Punchlist

Things I think need to be done in order to complete deprecation, ideally by 2019-03-31:

• send an announcement email to ruby-talk@
• notify maintainers of the webdrivers gem (/cc @titusfortner)
• notify rails-core contributors, as it's the largest reverse-dependency on this gem in the form of generate rails new projects
• update the README, CHANGELOG, and other project metadata
• release a patch version (likely v2.1.1) of the gem with a post-install message indicating that the gem is deprecated and out of support, and pointing users to webdrivers
• archive the git repository
• turn off CI at https://ci.nokogiri.org/teams/flavorjones/pipelines/chromedriver-helper and https://ci.nokogiri.org/teams/flavorjones/pipelines/chromedriver-helper-pr
• celebrate the gem's success and relax with a beer

[ioquatix]

Thanks for being an awesome maintainer.

[flavorjones]

v2.1.1 has been shipped with a post-install-message deprecation notice, and updated gemspec summary and description. Post-install message is:

  +--------------------------------------------------------------------+
  |                                                                    |
  |  NOTICE: chromedriver-helper is deprecated after 2019-03-31.       |
  |                                                                    |
  |  Please update to use the 'webdrivers' gem instead.                |
  |  See https://github.com/flavorjones/chromedriver-helper/issues/83  |
  |                                                                    |
  +--------------------------------------------------------------------+

[guilleiguaran]

Changed in Rails, new Rails 6.0.0 apps will ship webdrivers instead of chromedriver-helper

[flavorjones]

Rationale

1. I have not coded in Rails or used chromedriver in quite some time, and so I'm pretty far from the day-to-day needs of most users of chromedriver-helper. To be honest, there are some design decisions that need to be made, and work that needs to be done; and I don't have the well-formed opinions or the motivation that a daily user of the gem might have.
2. The webdrivers gem is well-maintained, is very nearly a superset of the functionality of this gem (and supports all major webdrivers), and further has maintainers interested in providing what little this gem does that's not already provided.
3. There's value to the community in having one well-supported and well-maintained gem that handles a given concern; and IMHO there is little-to-nothing to innovate on in this space.

[EverybodyKurts]

Just wanted to say thank you for this gem and the good work you did. This gem helped me run integration tests in chrome and I didn't have to do a lot of setup or config. Great job.

[nodanaonlyzuul]

Thanks @flavorjones (and everyone else who has contributed) - enjoy that well earned, final punch-list item.

[connorshea]

@flavorjones you should include a message in the Changelog as well.

[lazlyhu]

Huge respect because the just released post-install-message! 🏅

[flavorjones]

/cc @tenderlove for formal notification of rails-core contributors

[flavorjones]

ruby-talk notification is at http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-talk/440018

[pixeltrix]

@guilleiguaran should we also backport that to 5-2-stable as well?

[hybridspyda]

Trying to upgrade to using the webdrivers gem instead, running into issues:

Selenium::WebDriver::Error::UnknownError:
unknown error: Chrome failed to start: crashed
 (unknown error: DevToolsActivePort file doesn't exist)
 (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
 (Driver info: chromedriver=73.0.3683.68 (47787ec04b6e38e22703e856e101e840b65afe72),platform=Linux 4.4.0-17763-Microsoft x86_64)

My driver was previously setup and working using the following config:

require 'selenium-webdriver'
Capybara.register_driver :headless_chrome do |app|
	capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
		chromeOptions: { args: %w[headless disable-gpu] } # extras: no-sandbox disable-extensions
	)

	Capybara::Selenium::Driver.new(
		app,
		browser: :chrome,
		desired_capabilities: capabilities
	)
end
Capybara.javascript_driver = :headless_chrome
Capybara.current_driver = :headless_chrome

Thanks in advance!

[flavorjones]

@hybridspyda Please open an issue with the webdrivers gem.

[flavorjones]

CI pipelines have been deleted from https://ci.nokogiri.org/.

I'm about to archive this git repo, and so I'll ask you all to trust that this evening I will kick back with a beer as required in the punchlist above.