Update to tokio 1.0

[incker]

New version of tokio is released
rocket vesrion is 0.2 Cargo.toml

Chance to make breaking changes while rocket = "0.5" not released yet

[SergioBenitez]

We need hyper to upgrade first. In general, we're aware of new releases and will upgrade as soon as possible.

[krojew]

You can upgrade now and wrap hyper in a compatibility layer (tokio-compat-02) until they update.

[incker]

Looks like h2 have already received PR, see link
And the only blocker for hyper is h2see link

So, there is no reason to make compatibility layer. Looks like hyper updates will come soon

[protheory8]

Tokio 0.3 upgrade PR got merged into Hyper master branch recently, waiting for new Hyper release now?

[SergioBenitez]

@protheory8 That's right.

[jebrosen]

hyper 0.14.0 has just been released, targeting tokio 1.0 (released earlier today). The other blocker will be tokio-rustls (see tokio-rs/tls#46), and I will likely start tackling a migration PR today or Saturday.

[l4l]

@jebrosen mind if I work on this? Curious to look into the sources.

[jebrosen]

I already started and (maybe) finished it! - master...jebrosen:tokio1. But I don't think we should review/merge it quite yet, since a decent number of crates don't yet have releases for tokio 1.0. One is reqwest, which I want to be able to run some tests with, and @SergioBenitez has some work in progress on multipart handling that I think will also need a dependency update.

[Absolucy]

@jebrosen Reqwest already has a PR open: seanmonstar/reqwest#1076

[Absolucy]

Reqwest has just updated.