Tymon Tobolski

As you can read in #255, this issue is more complex than it seems. There are two workarounds: - Use [`Tesla.Mock.mock_global/1`](https://hexdocs.pm/tesla/Tesla.Mock.html#mock_global/1) (preferred) - Or skip including `Tesla.Middleware.Timeout` if `Mix.env ==...

Basically yes :) In case of tests it would be great to have failing test cases for all related issues and then check if changing to passive mode fixes them.

@mroach Currently the easiest option would be to use [`Tesla.client/2`](https://github.com/teamon/tesla#runtime-middleware) function to create a custom client for cases when you need something specific (and you can use that with any...

Right, currently the workaround would be to use for example ```ex adapter :hackney, recv_timeout: 30_000 ``` The general solution would mean "a middleware can set adapter-specific options" which does not...

Note for 1.0 users: You need to wrap adapter opts under `:adapter` key: ```ex adapter :hackney, recv_timeout: 30_000 # or MyClient.get("/", opts: [adapter: [recv_timeout: 30_000]]) ```

@sezaru Thanks for reporting this. Would you be able to provide a PR to fix this?

@crova Could you open a PR against current tesla master with the necessary changes?

Yes, with the patch that fixes the issue :)

To answer the [last comment from previous PR](https://github.com/teamon/tesla/pull/264#issuecomment-962813743) > I've also made a try on store_opts, as a mean to have "multi-tenant" caches, i.e., ServiceA and ServiceB each have their...

@andrewhr @tanguilp So... how can we move forward with this? :) (I just noticed I did a review but I've never pushed the "Publish review" button 🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️🤦‍♂️)