tor_error/retriable.rs
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353
//! Declare the `RetryTime` enumeration and related code.
use derive_more::{From, Into};
use std::{
cmp::Ordering,
time::{Duration, Instant},
};
use strum::EnumDiscriminants;
/// A description of when an operation may be retried.
///
/// # Retry times values are contextual.
///
/// Note that retrying is necessarily contextual, depending on what exactly
/// we're talking about retrying.
///
/// For an example of how context matters: suppose that we try to build a
/// circuit, and encounter a failure extending to the second hop. If we try to
/// build a circuit _through the same path_ immediately, it's likely to fail
/// again. But if we try to build a circuit through a different path, then
/// there's no reason to expect that same kind of error.
///
/// Thus, the same inner error condition ("failed to extend to the nth hop") can
/// indicate either a "Retry after waiting for a while" or "Retry immediately."
///
/// # Retry times depend on what we think might change.
///
/// Whether retrying will help depends on what we think is likely to change in
/// the near term.
///
/// For example, we generally assume an unreachable relay has some likelihood of
/// becoming reachable in the near future, and therefore connecting to such a
/// relay is worth retrying.
///
/// On the other hand, we _don't_ assume that the network is changing wildly
/// over time. Thus, if there is currently no relay that supports delivering
/// traffic to port 23 (telnet), we say that building a request for such a relay
/// is not retriable, even though technically such a relay might appear in the
/// next consensus.
#[derive(Copy, Clone, Debug, Eq, PartialEq, EnumDiscriminants)]
#[non_exhaustive]
// We define a discriminant type so we can simplify loose_cmp.
#[strum_discriminants(derive(Ord, PartialOrd))]
// We don't want to expose RetryTimeDiscriminants.
#[strum_discriminants(vis())]
pub enum RetryTime {
/// The operation can be retried immediately, and no delay is needed.
///
/// The recipient of this `RetryTime` variant may retry the operation
/// immediately without waiting.
///
/// This case should be used cautiously: it risks making code retry in a
/// loop without delay. It should only be used for error conditions that
/// are necessarily produced via a process that itself introduces a delay.
/// (For example, this case is suitable for errors caused by a remote
/// timeout.)
Immediate,
/// The operation can be retried after a short delay, to prevent overloading
/// the network.
///
/// The recipient of this `RetryTime` variant should delay a short amount of
/// time before retrying. The amount of time to delay should be randomized,
/// and should tend to grow larger the more failures there have been
/// recently for the given operation. (The `RetryDelay` type from
/// `tor-basic-utils` is suitable for managing this calculation.)
///
/// This case should be used for problems that tend to be "self correcting",
/// such as remote server failures (the server might come back up).
AfterWaiting,
/// The operation can be retried after a particular delay.
///
/// The recipient of this `RetryTime` variant should wait for at least the
/// given duration before retrying the operation.
///
/// This case should only be used if there is some reason not to return
/// `AfterWaiting`: for example, if the implementor is providing their own
/// back-off algorithm instead of using `RetryDelay.`
///
/// (This is a separate variant from `At`, since the constructor may not
/// have convenient access to (a mocked view of) the current time. If you
/// know that the current time is `now`, then `After(d)` is equivalent to
/// `At(now + d)`.)
After(Duration),
/// The operation can be retried at some particular time in the future.
///
/// The recipient of this this `RetryTime` variant should wait until the
/// current time (as returned by `Instant::now` or `SleepProvider::now` as
/// appropriate) is at least this given instant.
///
/// This case is appropriate for when we have a failure condition caused by
/// waiting for multiple other timeouts. (For example, if we believe that
/// all our guards are down, then we won't be able to try getting a guard
/// until the next time guard is scheduled to be marked as retriable.)
At(Instant),
/// Retrying is unlikely to make this operation succeed, unless something
/// else is fixed first.
///
/// The recipient of this `RetryTime` variant should generally give up, and
/// stop retrying the given operation.
///
/// We don't mean "literally" that the operation will never succeed: only
/// that retrying it in the near future without fixing the underlying cause
/// is unlikely to help.
///
/// This case is appropriate for issues like misconfiguration, internal
/// errors, and requests for operations that the network doesn't support.
///
/// This case is also appropriate for a problem that is "technically"
/// retriable, but where any resolution is likelier to take days or weeks
/// instead of minutes or hours.
Never,
}
/// A `RetryTime` wrapped so that it compares according to [`RetryTime::loose_cmp`]
#[derive(From, Into, Copy, Clone, Debug, Eq, PartialEq)]
pub struct LooseCmpRetryTime(RetryTime);
/// Trait for an error object that can tell us when the operation which
/// generated it can be retried.
pub trait HasRetryTime {
/// Return the time when the operation that gave this error can be retried.
///
/// See all caveats and explanations on [`RetryTime`].
fn retry_time(&self) -> RetryTime;
/// Return an absolute retry when the operation that gave this error can be
/// retried.
///
/// Requires that `now` is the current time, and `choose_delay` is a
/// function to choose a delay for [`RetryTime::AfterWaiting`].
fn abs_retry_time<F>(&self, now: Instant, choose_delay: F) -> AbsRetryTime
where
F: FnOnce() -> Duration,
Self: Sized,
{
self.retry_time().absolute(now, choose_delay)
}
}
/// An absolute [`RetryTime`].
///
/// Unlike `RetryTime`, this type always denotes a particular instant in time.
/// You can derive it using [`RetryTime::absolute`].
#[derive(Copy, Clone, Debug, Eq, PartialEq, Ord, PartialOrd)]
#[allow(clippy::exhaustive_enums)]
pub enum AbsRetryTime {
/// See [`RetryTime::Immediate`].
Immediate,
/// See [`RetryTime::At`].
At(Instant),
/// See [`RetryTime::Never`].
Never,
}
impl AbsRetryTime {
/// Construct an AbsRetryTime representing `base` + `plus`.
fn from_sum(base: Instant, plus: Duration) -> Self {
match base.checked_add(plus) {
Some(t) => AbsRetryTime::At(t),
None => AbsRetryTime::Never,
}
}
}
impl RetryTime {
/// Convert this [`RetryTime`] in to an absolute time.
///
/// Requires that `now` is the current time, and `choose_delay` is a
/// function to choose a delay for [`RetryTime::AfterWaiting`].
pub fn absolute<F>(self, now: Instant, choose_delay: F) -> AbsRetryTime
where
F: FnOnce() -> Duration,
{
match self {
RetryTime::Immediate => AbsRetryTime::Immediate,
RetryTime::AfterWaiting => AbsRetryTime::from_sum(now, choose_delay()),
RetryTime::After(d) => AbsRetryTime::from_sum(now, d),
RetryTime::At(t) => AbsRetryTime::At(t),
RetryTime::Never => AbsRetryTime::Never,
}
}
/// Convert all the provided `items` into [`AbsRetryTime`] values, and
/// return the earliest one.
///
/// Requires that `now` is the current time, and `choose_delay` is a
/// function to choose a delay for [`RetryTime::AfterWaiting`].
///
/// Differs from `items.map(AbsRetryTime::absolute(now,
/// choose_delay)).min()` in that it calls `choose_delay` at most once.
pub fn earliest_absolute<I, F>(items: I, now: Instant, choose_delay: F) -> Option<AbsRetryTime>
where
I: Iterator<Item = RetryTime>,
F: FnOnce() -> Duration,
{
let chosen_delay =
once_cell::unsync::Lazy::new(|| AbsRetryTime::from_sum(now, choose_delay()));
items
.map(|item| match item {
RetryTime::AfterWaiting => *chosen_delay,
other => other.absolute(now, || unreachable!()),
})
.min()
}
/// Return the "approximately earliest" item for an iterator of retry times.
///
/// This is necessarily an approximation, since we can't be sure what time
/// will be chosen if the retry is supposed to happen at a random time, and
/// therefore cannot tell whether `AfterWaiting` comes before or after
/// particular `At` and `After` instances.
///
/// If you need an exact answer, use earliest_absolute.
pub fn earliest_approx<I>(items: I) -> Option<RetryTime>
where
I: Iterator<Item = RetryTime>,
{
items.min_by(|a, b| a.loose_cmp(b))
}
/// A loose-but-total comparison operator, suitable for choosing a retry
/// time when multiple attempts have failed.
///
/// If you need an absolute comparison operator, convert to [`AbsRetryTime`] first.
///
/// See also:
/// [`LooseCmpRetryTime`], a wrapper for `RetryTime` that uses this comparison.
pub fn loose_cmp(&self, other: &Self) -> Ordering {
use RetryTime as RT;
match (self, other) {
// When we have the same type with an internal embedded duration or time,
// we compare based on the duration or time.
(RT::After(d1), RetryTime::After(d2)) => d1.cmp(d2),
(RT::At(t1), RetryTime::At(t2)) => t1.cmp(t2),
// Otherwise, we compare based on discriminant type.
//
// This can't do a perfect "apples-to-apples" comparison for
// `AfterWaiting` vs `At` vs `After`, but at least it imposes a
// total order.
(a, b) => RetryTimeDiscriminants::from(a).cmp(&RetryTimeDiscriminants::from(b)),
}
}
}
impl Ord for LooseCmpRetryTime {
fn cmp(&self, other: &Self) -> Ordering {
self.0.loose_cmp(&other.0)
}
}
impl PartialOrd for LooseCmpRetryTime {
fn partial_cmp(&self, other: &Self) -> Option<Ordering> {
Some(self.cmp(other))
}
}
#[cfg(test)]
mod test {
// @@ begin test lint list maintained by maint/add_warning @@
#![allow(clippy::bool_assert_comparison)]
#![allow(clippy::clone_on_copy)]
#![allow(clippy::dbg_macro)]
#![allow(clippy::mixed_attributes_style)]
#![allow(clippy::print_stderr)]
#![allow(clippy::print_stdout)]
#![allow(clippy::single_char_pattern)]
#![allow(clippy::unwrap_used)]
#![allow(clippy::unchecked_duration_subtraction)]
#![allow(clippy::useless_vec)]
#![allow(clippy::needless_pass_by_value)]
//! <!-- @@ end test lint list maintained by maint/add_warning @@ -->
use super::*;
#[test]
fn comparison() {
use RetryTime as RT;
let sec = Duration::from_secs(1);
let now = Instant::now();
let sorted = vec![
RT::Immediate,
RT::AfterWaiting,
RT::After(sec * 10),
RT::After(sec * 20),
RT::At(now),
RT::At(now + sec * 30),
RT::Never,
];
// Verify that these objects are actually in loose-cmp sorted order.
for (i, a) in sorted.iter().enumerate() {
for (j, b) in sorted.iter().enumerate() {
assert_eq!(a.loose_cmp(b), i.cmp(&j));
}
}
}
#[test]
fn abs_comparison() {
use AbsRetryTime as ART;
let sec = Duration::from_secs(1);
let now = Instant::now();
let sorted = vec![
ART::Immediate,
ART::At(now),
ART::At(now + sec * 30),
ART::Never,
];
// Verify that these objects are actually in loose-cmp sorted order.
for (i, a) in sorted.iter().enumerate() {
for (j, b) in sorted.iter().enumerate() {
assert_eq!(a.cmp(b), i.cmp(&j));
}
}
}
#[test]
fn earliest_absolute() {
let sec = Duration::from_secs(1);
let now = Instant::now();
let times = vec![RetryTime::AfterWaiting, RetryTime::Never];
let earliest = RetryTime::earliest_absolute(times.into_iter(), now, || sec);
assert_eq!(
earliest.expect("no absolute time"),
AbsRetryTime::At(now + sec)
);
}
#[test]
fn abs_from_sum() {
let base = Instant::now();
let delta = Duration::from_secs(1);
assert_eq!(
AbsRetryTime::from_sum(base, delta),
AbsRetryTime::At(base + delta)
);
assert_eq!(
AbsRetryTime::from_sum(base, Duration::MAX),
AbsRetryTime::Never
);
}
}