Upgrade to tokio v1.0 #354
Comments
zonyitoo
added a commit
that referenced
this issue
Dec 24, 2020
- removed tokio::prelude - upgrade hyper to v0.14, tokio-rustls to v0.22 still working on migrating trust-dns-* and tokio-native-tls ref #354
zonyitoo
added a commit
that referenced
this issue
Dec 24, 2020
This was referenced Dec 24, 2020
Closed
Closed
|
剩下的两个应该都在上游解决了～ |
|
https://github.com/bluejekyll/trust-dns/blob/main/crates/resolver/Cargo.toml#L80 trust-dns didn't update yet. |
|
1.0.0 was replaced with 1.0.1 which fixed a soundness hole https://github.com/tokio-rs/tokio/releases/tag/tokio-1.0.1 |
|
It doesn't matter, we don't need this |
zonyitoo
added a commit
that referenced
this issue
Dec 28, 2020
* upgrade to tokio v1.0 - removed tokio::prelude - upgrade hyper to v0.14, tokio-rustls to v0.22 still working on migrating trust-dns-* and tokio-native-tls ref #354 * tokio v1.0 removed with_poll fix #355, ref #354 * removed CTRL-BREAK signal handler ref #354 * fixes compliation error, add missing return fixes #355 * allow setting SO_SNDBUF and SO_RCVBUF for sockets ref #352 * completely removed unix socket based DNS resolving ref shadowsocks/shadowsocks-android#2622 * fix build issue on Windows * fixed uds poll_write loop, fixed udp outbound loopback check ref #355 * disable default trust-dns resolver for andorid, macos, ios This commit also: - Optimized resolve() logging with elapsed time - updated tokio-native-tls * local-dns removed from default features * fix rustc version with rust-toolchain * Bump bytes from 0.6.0 to 1.0.0 * add dependabot badge * indirectly depend on trust_dns_proto via trust_dns_resolver * auto reconnect if udp sendto failed * recreate proxied socket if recv() returns failure * increase score precision to 0.0001 * example of log4rs configuration * PingBalancer instance shouldn't kill probing task when dropping - Probing task should be controlled by the internal shared state * switch to trust-dns main for latest tokio 1.0 support
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: