Faraday::TimeoutError being raised without stacktrace
jesse-smidt opened this issue · comments
Hello!
We've been noticing some interesting behavior after upgrading from 4.0.0 to 11.0.0 of this gem.
After bumping this gem we started to notice that what was once raised as Net::ReadTimeout is now raised as a Faraday::TimeoutError. This error occurs when a request to plaid is not completed after 10 minutes as has been configured by default (https://github.com/plaid/plaid-ruby/blob/abdc9f6644d2dce5536f6f86ea4d149c2bda8e1c/lib/plaid/middleware.rb). This in itself is not a problem, however, this error no longer includes a stacktrace, meaning that we have no way of knowing where, in our code, the error was raised.
Would it be possible to include a stacktrace with this error?
Closing this issue because v14 of the library is a total rewrite and we don't have any info on whether this issue reproduces there. If you experience this issue on v14, please feel free to reopen!