wip(feat(bitreq)): switch from minreq/reqwest to bitreq HTTP client

[oleonardolima]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 18927210446

Details

• 8 of 9 (88.89%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 87.216%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/blocking.rs	7	8	87.5%

Totals
Change from base Build 18851490484:	0.0%
Covered Lines:	1037
Relevant Lines:	1189

---

💛 - Coveralls

[tnull]

@oleonardolima Any update here? The rust-esplora-client might be the last thing that keeps reqwest (and sub-dependencies) in our tree. If you don't have time to finish this, should I take this one over?

[oleonardolima]

@oleonardolima Any update here? The rust-esplora-client might be the last thing that keeps reqwest (and sub-dependencies) in our tree. If you don't have time to finish this, should I take this one over?

@tnull I didn't follow the recent changes for the latest bitreq release, do you deem it production-ready and with the feature-parity that we need from reqwest here ?

[tnull]

@oleonardolima Any update here? The rust-esplora-client might be the last thing that keeps reqwest (and sub-dependencies) in our tree. If you don't have time to finish this, should I take this one over?

@tnull I didn't follow the recent changes for the latest bitreq release, do you deem it production-ready and with the feature-parity that we need from reqwest here ?

Yes, we made good progress there (full/fixed async support, added a Url type for parsing, superseding url::Url, etc). Also replaced other HTTP clients in a bunch of places (LDK Node, LDK, alpenlabs/bitcoind-async-client etc). So would be great to move forward with this here, too!