Closed jekku closed 2 years ago
Commenting some snaps with the whole stacktrace from the platform that stores our exceptions just in case it helps
Thank you! It seems this bug needs to be patched upstream instead, by whatever is actually returning the invalid tuple, no? :)
That seems to be reasonable. Further justified by the move to Finch as well. Just wondering currently when we'll might get a release and some docs on the newer version? :)
Closing this now.
Please do try it out and let us know it works, that will certainly get us closer to a new release. Thank you!
What's here?
This PR is for the current version of the library.
In the current version of this library (v0.7.1), when
receive_messages/3
is invoked, we sometimes receive this kind of error tuple with 3 members:The stacktrace from the exception thrown from the library looks like this:
What we've checked and tried
{:error, Tesla.env()}
tuple, there are still times where a tuple of 3 members appears