Skip to content
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

Attempt to fix Ferrum timeout errors #1877

Merged
merged 5 commits into from
Oct 19, 2023
Merged

Attempt to fix Ferrum timeout errors #1877

merged 5 commits into from
Oct 19, 2023

Conversation

camertron
Copy link
Contributor

What are you trying to accomplish?

We're seeing quite a few Ferrum::ProcessTimeoutError: Browser did not produce websocket url within 10 seconds errors in CI jobs. I did a little digging and discovered the Cuprite driver we're registering in test_helper.rb is getting overwritten by Rails, so it's not using any of the config options we're passing in.

What approach did you choose and why?

primer/view_components solved this a while ago by registering a driver with a unique name, so that's what I did here.

@camertron camertron merged commit dea2697 into main Oct 19, 2023
@camertron camertron deleted the fix_ferrum_timeouts branch October 19, 2023 20:11
mkllnk added a commit to mkllnk/openfoodnetwork that referenced this pull request Nov 2, 2023
Rails is registering a driver called `cuprite`. And when we did that as
well the driver got registered three times somehow. It looked like our
driver options were used in the end but just to clarify I gave it a
unique name.

This was inspired by:

* ViewComponent/view_component#1877

It suggests that it may avoid dead browser errors on CI. We'll see.
claudiob pushed a commit to claudiob/view_component that referenced this pull request Dec 22, 2023
* Attempt to fix Ferrum timeout errors

* Add CHANGELOG entry; fix linting issues
claudiob pushed a commit to claudiob/view_component that referenced this pull request Jan 3, 2024
* Attempt to fix Ferrum timeout errors

* Add CHANGELOG entry; fix linting issues
fleblond07 pushed a commit to fleblond07/openfoodnetwork that referenced this pull request Mar 13, 2024
Rails is registering a driver called `cuprite`. And when we did that as
well the driver got registered three times somehow. It looked like our
driver options were used in the end but just to clarify I gave it a
unique name.

This was inspired by:

* ViewComponent/view_component#1877

It suggests that it may avoid dead browser errors on CI. We'll see.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant