woohaaha
Workaround for Wallaby HTTPoison error
I am getting the error listed here https://github.com/elixir-wallaby/wallaby/issues/365 reliably ~50% of the time.
Anyone here have a workaround that may not have been discussed in this thread?
Thank you
Update:
Making async false and adding a sleep (~200ms) around every click/visit doesn’t make a difference. Tests passing < 50% of time with the same error:
(RuntimeError) Wallaby had an internal issue with HTTPoison:
%HTTPoison.Error{id: nil, reason: :timeout}
Most Liked
padjo
had this error
" test login --core test (Devato.Features.IndexPageTest)
test/devato_web/features/index_page_test.exs:13
** (RuntimeError) Wallaby had an internal issue with HTTPoison:
%HTTPoison.Error{id: nil, reason: :timeout}
stacktrace:
(wallaby 0.23.0) lib/wallaby/httpclient.ex:37: Wallaby.HTTPClient.make_request/5
(wallaby 0.23.0) lib/wallaby/experimental/chrome.ex:96: Wallaby.Experimental.Chrome.start_session/1
(wallaby 0.23.0) lib/wallaby.ex:78: Wallaby.start_session/1
(devato 0.1.0) test/support/feature_case.ex:25: Devato.FeatureCase.__ex_unit_setup_0/1
(devato 0.1.0) test/support/feature_case.ex:1: Devato.FeatureCase.ex_unit/2
test/devato_web/features/index_page_test.exs:1: Devato.Features.IndexPageTest.ex_unit/2"
i could run the tests chrome headless but i needed it to work so i can see it running on the browser . What worked for me was configuring the timeouts
added
config :wallaby,
hackney_options: [timeout: :infinity, recv_timeout: :infinity]
Overriding a value
config :wallaby,
hackney_options: [timeout: 5_000]
hope this helps others







