Andrea Leopardi

> `%Mint.TransportError{reason: %Mint.TransportError{reason: :timeout}}` This is definitely an error yeah. I'll try to take a look.

@jozuas no, didn't have time to look at this. Want to give it a try? Usually we call functions like `wrap_error` and we must be calling it on an already-wrapped...

@jozuas sounds fantastic, thank you.

@cgarvis we already have [a PR](https://github.com/getsentry/sentry-elixir/pull/897) that replaces Hackney with Finch. I think that's a preferred route—this is not exposed to users and using Req means using one more dependency,...

@cgarvis I think I’m missing the point of having another adapter then. Why would someone care about the adapter that the SDK uses unless it's for dependencies reasons?

@Th3-M4jor yes adding that to CI would totally be feasible. As for the native type, I assume it's not documented in the v4 native protocol from C* right? Also, I...

@PragTob hiya! Thanks for the bunny. I think we should go ahead and implement load shedding and thresholds like we do for `Sentry.LoggerHandler`: https://github.com/getsentry/sentry-elixir/blob/master/lib/sentry/logger_handler.ex#L65-L107 However, this falls in the hands...

I think we should add `challenge_response_body` and not change the existing callback, so that we can make the behavior backwards compatible. We can make the new callback optional, and if...

Nice discussion thank you. I think we should do this in Mint if possible, and bubble it up to Finch/Req. I think the idea of a struct that 1. Implements...

I think it's a practical solution that can evolve into a language feature eventually (`Mint.redact` would start returning the language struct instead of the Mint-specific one).