Skip to content

Elastic APM v4.7.0 breaks versions of Faraday < 1.3.0 #1418

Closed
@ryanwi

Description

@ryanwi

In an application with Faraday v0.17.4, experienced new errors after upgrading the Elastic APM gem from v4.6.0 to v4.7.0. Elastic APM is looking for a response_status on Faraday errors that does not exist in older versions of Faraday.

errors were:

undefined method `response_status' for #<Faraday::TimeoutError:0x00007f401377b2d0>
undefined method `response_status' for #<Faraday::SSLError:0x00007fbcac2e7960>
undefined method `response_status' for #<Faraday::ConnectionFailed:0x00007fae7dcd8420> 

Here is the change in v4.7.0: v4.6.0...v4.7.0#diff-4b5630a4907f497d4416de76c8dd5a162f4a525222dc3c11bdcef2182a9cdbcdR112

response_status was introduced to Faraday in this commit: lostisland/faraday@023cc41 and is only available in faraday versions >= 1.3.0

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions