Closed gustavowd closed 1 month ago
If you use embassy-net from crates.io, you should probably stick to reqwless 0.12.1. If you use patched git dependencies for embassy-net, if you use the latest rev, you should be able to use 0.13.0
Thanks @lulf . I'm using a local copy of crates.io embassy-net. I update the embedded_nal_async crate in this local copy and now is everything working like a charm.
Hi. I update reqwless to version 1.3.0 in my esp32-c3 project and start to receive several compilation erros:
TcpClient<'_, WifiDevice<'static, WifiStaDevice>, 1, 4096, 4096>: embedded_nal_async::stack::tcp::TcpConnect
is not satisfied --> src/http.rs:103:51embedded_nal_async::stack::tcp::TcpConnect
is not implemented forTcpClient<'_, WifiDevice<'static, WifiStaDevice>, 1, 4096, 4096>
embedded_nal_async
are being used? = help: the traitembedded_nal_async::stack::tcp::TcpConnect
is implemented for&T
note: required by a bound inHttpClient::<'a, T, D>::new_with_tls
--> /home/gustavo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwless-0.13.0/src/client.rs:99:8HttpClient::<'a, T, D>::new_with_tls
... 114 | pub fn new_with_tls(client: &'a T, dns: &'a D, tls: TlsConfig<'a>) -> Self { | ------------ required by a bound in this associated function
TcpClient<'_, WifiDevice<'static, WifiStaDevice>, 1, 4096, 4096>: embedded_nal_async::stack::tcp::TcpConnect
is not satisfied --> src/http.rs:103:26embedded_nal_async::stack::tcp::TcpConnect
is not implemented forTcpClient<'_, WifiDevice<'static, WifiStaDevice>, 1, 4096, 4096>
embedded_nal_async
are being used? = help: the traitembedded_nal_async::stack::tcp::TcpConnect
is implemented for&T
note: required by a bound inHttpClient
--> /home/gustavo/.cargo/registry/src/index.crates.io-6f17d22bba15001f/reqwless-0.13.0/src/client.rs:20:8HttpClient
DnsSocket<'_, WifiDevice<'static, WifiStaDevice>>: embedded_nal_async::dns::Dns
is not satisfied --> src/http.rs:103:64embedded_nal_async::dns::Dns
is not implemented forDnsSocket<'_, WifiDevice<'static, WifiStaDevice>>
help: trait impl with same name found
Seems to be something related with embedded-nal-async: " note: perhaps two different versions of crate
embedded_nal_async
are being used?"Any thoughts on this issue?