Upgrade dependencies to tokio 1.0

[fanatid]

tokio:0.3 was released a month ago. dependabot creates pull requests (like #5158) with dependencies which were already updated, but we can not easily merge them. I did not research yet about any compatibility layer, maybe we will need to update everything at once or it will be possible to update crates independently, not sure. This is only a tracking issue with dependencies status regarding their update to new tokio.

tokio:0.3 list (outdated because we will upgrade to tokio:1.0 and skip tokio:0.3):

**Valid on `11/30/2020`:**

• async-compression (tokio:0.3 — ✔️ >=0.3.6 Tokio 0.3 support Nullus157/async-compression#104)
• bollard (tokio:0.3 — ❌ Release plan for support on tokio v0.3? fussybeaver/bollard#130)
• goauth (tokio:0.3 — ❌ Release plan for support on tokio v1.0? durch/rust-goauth#16)
• h2 (tokio:0.3 — ✔️, git, >=0.3.0 Release plan for support on tokio v0.3? hyperium/h2#499), not a direct dependency
• hyper-openssl (tokio:1.0 — ✔️ Release plan for support on tokio v0.3? sfackler/hyper-openssl#29)
• hyper-rustls (tokio:0.3 — ✔️, git, Support for tokio0.3 rustls/hyper-rustls#123), not a direct dependency
• hyper-tls (tokio:0.3 — ❌ Upgrade to hyper 0.14 hyperium/hyper-tls#76), not a direct dependency
• hyper-unix-connector (tokio:1.0 - ✔️, Release plan for support on tokio v0.3? akshayknarayan/hyper-unix-connector#2), not a direct dependency
• hyper (tokio:0.3 — ✔️, git, >=0.14.0 Upgrade to Tokio v0.3 hyperium/hyper#2302 milestone: https://github.com/hyperium/hyper/milestone/6)
• lib/file-source (tokio:0.3 — ❌)
• lib/vector-api-client (tokio:0.3 — ❌)
• mongodb (tokio:0.3 — ❌ Tokio 1.0 compatibility mongodb/mongo-rust-driver#267)
• pulsar (tokio:0.3 — ❌ Tokio 0.3? streamnative/pulsar-rs#121)
• rdkafka (tokio:0.3 — ✔️, git, >0.25.0 Migration to tokio 0.3 fede1024/rust-rdkafka#298)
• reqwest (tokio:0.3 — ❌ Update tokio to 1.0 seanmonstar/reqwest#1060)
• rusoto_* (tokio:0.3 — ❌ Update tokio to 1.0 rusoto/rusoto#1845)
• stream-cancel (tokio:0.3 — ✔️ Upgrade to tokio 0.3 jonhoo/stream-cancel#8)
• tokio-native-tls (tokio:0.3 — ✔️ native: Upgrade tokio and prepare 0.2 release tokio-rs/tls#31), not a direct dependency
• tokio-openssl (tokio:0.3 — ✔️ Update to tokio 0.3 tokio-rs/tokio-openssl#21), not a direct dependency
• tokio-test (tokio:0.3 — ✔️ chore: prepare for v0.3 breaking changes tokio-rs/tokio#2747)
• tokio-tls (tokio:0.3 — ❌), not a direct dependency
• tokio-tungstenite (tokio:0.3 — ✔️ Update tokio to 0.3 snapview/tokio-tungstenite#125), not a direct dependency
• tokio-util (tokio:0.3 — ✔️ chore: prepare for v0.3 breaking changes tokio-rs/tokio#2747)
• tower-test (tokio:0.3 — ✔️, git, update to Tokio 0.3 tower-rs/tower#476)
• tower (tokio:0.3 — ✔️, git, update to Tokio 0.3 tower-rs/tower#476)
• trust-dns-proto (tokio:0.3 — ✔️, alpha released, https://github.com/bluejekyll/trust-dns/pull/1262), not a direct dependency
• trust-dns-resolver (tokio:0.3 — ✔️, alpha released, https://github.com/bluejekyll/trust-dns/pull/1262), not a direct dependency
• warp (tokio:0.3 — ❌ Upgrade to Tokio v1 seanmonstar/warp#725)

Will create new list (with tokio:1.0) when we close #5103.

[binarylogic]

@kirillt it might be worth opening issues on each repo first if they don't already exist. Would you mind doing that?

[kirillt]

@fanatid :)

[fanatid]

@binarylogic I updated the issue (tracking issues added). Before we start work on tokio upgrade I think we need to finish with futures: #5103 (maybe add blocking tag here?).

[binarylogic]

Thanks @fanatid, sounds good.

[juchiast]

tokio 1.0 is out!

[fanatid]

Yep, maybe we will skip 0.3 and switch directly to 1.0. I'm not sure that all listed crates above will support 0.3...
https://tokio.rs/blog/2020-12-tokio-1-0

[juchiast]

Yeah, hyper already released 1.0-compatible version, and I think warp will be updated soon.

[jamtur01]

Look like go-auth has released 0.9.0 which upgrades to tokio 1.0

[fanatid]

@lukesteensen started work on this in #5872