Update to tokio 1.0 ecosystem

Question

Update to tokio 1.0 ecosystem

Jake-Shadle opened this issue 3 years ago · comments

Now that tokio 1.0 is out, and hyper/reqwest have been updated, it would be good to move to them, especially now that it is easier due to #161 has been merged, and the only holdout is azure.

Moss · Answer 1 · Sun Jan 31 2021 14:40:38 GMT+0800 (China Standard Time)

Hi @Jake-Shadle, I'm trying to implement an Azure blob API lib, https://github.com/m0ssc0de/bloblock. I reckon it will help the cargo-fetcher update to tokio 1.0.
My project is in the very initial stage. So if you have time, I'm glad to hear your suggestions.

Jake Shadle · Answer 2 · Mon Feb 01 2021 21:39:52 GMT+0800 (China Standard Time)

I don't have time to look at the exact code at the moment, but one thing that would make it a lot easier to review a future change that uses the crate would be if the crate itself was tested with the Storage Emulator. I would probably want to add storage emulator tests to cargo-fetcher as well, but knowing the library was tested with it would at least be a really good start IMO.

Moss · Answer 3 · Mon Mar 01 2021 22:14:06 GMT+0800 (China Standard Time)

Yeah. Testing with the real Azure service is a little bit hard. I will try to find an appropriate solution for the Storage Emulator.