-
Notifications
You must be signed in to change notification settings - Fork 324
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
HTTP 5.0 no longer supports VCR #672
Comments
It seems like for the purposes of VCR, which is trying to simulate how real-world requests behave, it should probably start passing We could potentially allow |
I get your point. So maybe I should open an issue in there? Sorry I am no specialist in this matter and my first thought was to do it in here as in previous HTTP.rb versions it worked fine, and it is also working fine in other libraries |
IIRC VCR uses webmock (haven't used it in awhile, sorry) so that would probably be the right place to enquire about this. There might already be a relevant issue. |
👋🏽 @hugopassos this was fixed in bblimke/webmock#940 Update webmock to 3.13.0 |
Awesome, thanks! |
@cesc1989 thanks! |
As a result of #546, requests made with VCR are now raising the error
KeyError: key not found: :request
as the parameterrequest
is not sent by it:The error will be raised at
/lib/http/response.rb:46
Can't it behave like an optional parameter like it was in the previous version of the gem?
The text was updated successfully, but these errors were encountered: