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

Fix 1.8 and make ci pass #557

Merged
merged 4 commits into from
Dec 27, 2015

Conversation

davidbegin
Copy link
Collaborator

No description provided.

@davidbegin davidbegin force-pushed the fix-1.8-and-make-CI-pass branch 9 times, most recently from e6cfef9 to 853b3b3 Compare December 22, 2015 20:00
@davidbegin davidbegin force-pushed the fix-1.8-and-make-CI-pass branch 2 times, most recently from e6b5764 to d9ec549 Compare December 23, 2015 08:22
@davidbegin
Copy link
Collaborator Author

I still need to figure out what has changed to cause this spec to start failing in the first place.
I tried to create the exact dependencies from a passing Travis CI build, but the spec was still failing.

But now I have a better idea of where the change must be coming from, RSpec.

@matthewrudy
Copy link
Contributor

@davidbegin no worries.
Thanks for your time.

I'll leave these issues in your hands.

It works fine in our app running curb 0.9.0 and Ruby 2.2.2
But just get some devs worrying about the warning,
so thought it was worth exploring.

Thanks for your help.

@davidbegin davidbegin force-pushed the fix-1.8-and-make-CI-pass branch 2 times, most recently from 95663b4 to 4016323 Compare December 23, 2015 21:59
  For some reason on JRuby this spec started causing a
  ArgumentError: Invalid byte sequence in UTF-8

  The failing spec is ensuring that when WebMock is off, it is possible to query to a real
  website, in this case google.

  The spec queries google, and then ensures the body of the response
  contains google.

  So all this fix does is force the response to be UTF, and get rid of
  any invalid characters. So now match can check for google in the provided string,
  without worrying about invalid characters it doesn't know how to handle.

  While knowing why we have to suddenly force encoding would be ideal,
  we know this change does not affect the integrity of the spec.
davidbegin added a commit that referenced this pull request Dec 27, 2015
@davidbegin davidbegin merged commit e05d49b into bblimke:master Dec 27, 2015
@davidbegin davidbegin deleted the fix-1.8-and-make-CI-pass branch December 27, 2015 04:17
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.

2 participants