tokio: update to mio 0.7

[carllerche]

Mio 0.7 is not yet released. The tokio master branch should depend on the mio master branch and track changes.

[Razican]

Hello, is there news on this regard?

[carllerche]

It is a goal for 0.3, which should be sometime next month. There are still some windows issues to work through.

[galich]

Current version of tokio refers to winapi 0.3 and mio 0.6, which refers to winapi 0.2. We have 2 versions of fairly large winapi crate to build every time.

@carllerche is there any specific issue we can try and help with to make mio 0.7 used in tokio faster?

[Emilgardis]

mio 0.7.0 is now released. tokio-rs/mio#1279
Is there a timeline done for this?

[Stammark]

+1 for this from me!

Although to resolve winapi issues, the mio-named-pipes dependency would also have to be updated, too, probably (?) (see bbqsrc/mio-named-pipes#7).

edit: Thank you @Darksonn , sorry I hadn't spotted the other issue!

[Darksonn]

Regarding mio-named-pipes: #2547

[Darksonn]

oops

[jmagnuson]

PR for updating mio-named-pipes: bbqsrc/mio-named-pipes#10

Previous work to update tokio to mio 0.7: #1767

[damianwadley]

Note that mio 0.6 contains an indirect dependency (via miow 0.2) on net2, which has been deprecated in favor of socket2 since earlier this month. cargo audit is also warning about it.
mio 0.7 (miow 0.3) has already moved to socket2.

[oherrala]

Borrowing this issue to mention that mio 0.7.0 release fixes a memory leak in Windows.

Upstream issue: tokio-rs/mio#919

Issues hopefully solved by updating tokio's mio to 0.7.0 based on the issue and crate's dependency to tokio:

• https://github.com/bluejekyll/trust-dns/issues/692
• reqwest never close socket connection in windows ! seanmonstar/reqwest#284
• GRPC Client on windows doesn't close TCP connection on drop. stepancheg/grpc-rust#110

[faern]

Any updates here? Getting rid of mio 0.6 is certainly desirable.

[carllerche]

Planned as part of 0.3

[taiki-e]

Closing -- done in #2893