How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
Whether err is a conditional write refused: the name is taken, or another write
was racing for it.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
Whether an error of this kind is worth retrying as is, by the rule on
s3_error_kind: the network and a busy store, yes; anything else, no.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
The kind for an S3 error known only by its code — as a DeleteObjects that
succeeded reports each key it could not delete, with a code and no status.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
How hyperfile classifies an error, and which kinds are worth retrying — the
rule on s3_error_kind.
Map an S3 SDK error to the semantically closest std::io::ErrorKind so
callers (and crates layered on top of hyperfile) can react precisely
instead of treating every S3 failure as an opaque Other: