Open kanejamison opened 2 weeks ago
I'll add in a quick note here that which chrome
and which chromedriver
appears to be running successfully when our team connects via CLI, so please feel free to close if this ticket might be better for Ferrum repo.
It seems like CDP / Chrome Devtools Protocol (apparently used by Ferrum) somehow broke with Chrome v128.
We heard reports of this issue with Selenium, and have a PR open with a draft fix/workaround.
I personally do not know much about exactly what changed in CDP, but maybe this context can help you find the cause.
I switched over from
heroku/google-chrome
this week and followed the instructions on Migrating from Separate Buildpacks (though I used the Heroku app settings UI to remove and add the new buildpacks instead of CLI):Since then we have a cron job running screenshots using Ferrum that has started failing with the following error:
ERROR taking screenshot: Browser did not produce websocket url within 10 seconds, try to increase
:process_timeout. See https://github.com/rubycdp/ferrum#customization
Actions I've taken to try and resolve:
BROWSER_PATH
ENV VAR to/app/.chrome-for-testing/chrome-linux64/chrome
in case the path wasn't getting picked up somehow.Are there any clear gotchas I should be looking for related to the buildpack usage or migration that I'm missing?
Relevant app settings:
Here's the script I'm running that is failing in case it's helpful. We don't have a specific Ferrum config outside of this call to
Ferrum::Browser.new()
. The finalrescue StandardError => e
is where my exception is getting tracked.Thanks for any assistance - I know this is on the support edge between the buildpack and the gem itself, but since the buildpack is what I'm migrating I wanted to start by posting here.