Closed gingerlime closed 7 years ago
Specs pass for me locally. Why are you running against webmock 2.3.2? The Gemfile.lock specifies 1.24.2, and the different gem versions may be what's causing the failures.
There's no Gemfile.lock
file in the repo... And I think travis is also showing similar failures, no?
Whoops, of course there isn't a Gemfile.lock, I forgot that it's not supposed to be committed for gems. So our gemspec is too lax with the dev dependencies, which should be fixed.
The Travis failures I looked at aren't related: they're caused by not updating the mock requests for the changes you made in the PR. But I see that on builds for newer Rubies we're hitting the same issue, which again I think is a gemspec bug. Will investigate, thanks!
Some early failures were my mistake (although I couldn't test it locally, so it was kinda unavoidable). But I think the most recent build failed due to similar issues as I reported here. I didn't check thoroughly, because there's a lot of noise.
I'm trying to run specs on this project, and most of them fail on a similar error
It looks like the client no longer passes the SITE_ID and API_KEY in the URL, but rather adds a basic authentication
Authorization
header, but the tests weren't updated to reflect this?