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

Unable to record when specifying a receive_timeout option #208

Closed
daveshah opened this issue Aug 8, 2023 · 0 comments · Fixed by #209
Closed

Unable to record when specifying a receive_timeout option #208

daveshah opened this issue Aug 8, 2023 · 0 comments · Fixed by #209

Comments

@daveshah
Copy link
Contributor

daveshah commented Aug 8, 2023

Description

Increasing the timeout by supplying the receive_timeout (or recv_timeout dependent on the client) option produces the below error when the call is being recorded and saved.
This issue was reproduced with both the Hackney adapter as well as the Finch adapter.

The client call when using the Hackney adapter looks similar to:
HTTPoison.post(@endpoint, body, headers , [recv_timeout: 60_000]
And produces:

    ** (FunctionClauseError) no function clause matching in String.valid?/2

     The following arguments were given to String.valid?/2:
     
         # 1
         60000
     
         # 2
         :default
     
     Attempted function clauses (showing 2 out of 2):
     
         def valid?(<<string::binary>>, :default)
         def valid?(<<string::binary>>, :fast_ascii)
     
     code: assert {:ok, %{status: 200}} = Api.create_submission(valid_request_body)
     stacktrace:
       (elixir 1.15.4) lib/string.ex:1827: String.valid?/2
       (exvcr 0.14.2) lib/exvcr/filter.ex:10: ExVCR.Filter.filter_sensitive_data/1
      ...
daveshah added a commit to CoveredInsurance/exvcr that referenced this issue Aug 8, 2023
parroty pushed a commit that referenced this issue Aug 9, 2023
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 a pull request may close this issue.

1 participant