You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem because in a service that uses a lower tier API than the service itself, a dependency inversion of tiers can happen. For example, a tier 2 service calling a tier 3 service.
The tier inversion happens because we are not rescuing the error and returning it into a tuple, so the operation can work without problems under this situation.
Problem
When using Finch is expected to receive a RuntimeError if the connection pool is exhausted, see https://github.com/sneako/finch/blob/main/test/finch_test.exs#L561
This is a problem because in a service that uses a lower tier API than the service itself, a dependency inversion of tiers can happen. For example, a tier 2 service calling a tier 3 service.
The tier inversion happens because we are not rescuing the error and returning it into a tuple, so the operation can work without problems under this situation.
Proposed solution
For clients using Tesla: elixir-tesla/tesla#744
Unresolved questions
reraise
should be changed to return an error tuple instead, so we don't provoke the linked caller to exit?cc/ @yordis @sneako
The text was updated successfully, but these errors were encountered: