Kong / Kong/unirest-ruby

Upgrading to Rails 4.2.7 breaks funcitonality.

Open
#41 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
364
Forks
76
PR merge metrics
No merged PRs in 30d

Description

Using Rails 4.2.7 caused my connection to mashape that I use in my seed file to fail and generates the warning:

[warning] The response contained in an RestClient::Exception is now a RestClient::Response instead of a Net::HTTPResponse, please update your code

Downgrading to 4.2.6 fixes issue. Not sure it's an actual Unirest issue or a Rails issue, so posting just FYI.

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Reproduce the Mashape connection from the seed file under Rails 4.2.7 and 4.2.6, then trace the RestClient::Exception warning to determine whether Unirest is affected. Done means identifying the responsible project and documenting or fixing the compatibility behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.