-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hyper-util on xtensa #3684
Comments
Looks like someone would need to add support however which way to that file. If that platform doesn't support the TCP options, than the |
Corresponding issue in |
I changed like this and it's compiling, but I don't know if it's going to work properly. impl TcpKeepaliveConfig {
} |
That should do the trick for the |
I'm trying to use hyper-util and hyper on esp32s3 but I have these errors, can anyone help me?
error[E0599]: no method named
with_interval
found for structTcpKeepalive
in the current scope--> C:\Users\lpirc.cargo\registry\src\index.crates.io-6f17d22bba15001f\hyper-util-0.1.5\src\client\legacy\connect\http.rs:114:12
|
114 | ka.with_interval(interval)
| ^^^^^^^^^^^^^ method not found in
TcpKeepalive
error[E0599]: no method named
with_retries
found for structTcpKeepalive
in the current scope--> C:\Users\lpirc.cargo\registry\src\index.crates.io-6f17d22bba15001f\hyper-util-0.1.5\src\client\legacy\connect\http.rs:130:12
|
130 | ka.with_retries(retries)
| ^^^^^^^^^^^^ help: there is a method with a similar name:
with_time
}
this is where in http.rs I get errors:
impl TcpKeepaliveConfig {
/// Converts into a
socket2::TcpKeealive
if there is any keep alive configuration.fn into_tcpkeepalive(self) -> Option {
let mut dirty = false;
let mut ka = TcpKeepalive::new();
if let Some(time) = self.time {
ka = ka.with_time(time);
dirty = true
}
if let Some(interval) = self.interval {
ka = Self::ka_with_interval(ka, interval, &mut dirty)
};
if let Some(retries) = self.retries {
ka = Self::ka_with_retries(ka, retries, &mut dirty)
};
if dirty {
Some(ka)
} else {
None
}
}
}
The text was updated successfully, but these errors were encountered: