Enum ExternalCarryError 

#[non_exhaustive]
pub enum ExternalCarryError {
    UnknownFile {
        file_id: FileId,
    },
    DuplicateFile {
        file_id: FileId,
    },
    UncoveredFile {
        file_id: FileId,
    },
    SliceCountMismatch {
        file_id: FileId,
        expected: usize,
        supplied: usize,
    },
    DamagedCountMismatch {
        file_id: FileId,
        declared: u32,
        actual: u32,
    },
    IncompleteCompleteFile {
        file_id: FileId,
    },
    MissingFileWithContent {
        file_id: FileId,
    },
    UnfingerprintedFile {
        file_id: FileId,
    },
    RelocatedFile {
        file_id: FileId,
    },
    Set(Par2Error),
}

Why a host’s verification could not be turned into a ScanCarry.

Every variant names a disagreement between the attestation and the set it claims to describe, not a property of the files on disk. They are caller bugs — a mismatched set, an attestation that contradicts itself — and are reported rather than absorbed, because a carry built from an attestation this crate could not make sense of is exactly the thing that must never reach a repair.

Variants (Non-exhaustive)

Non-exhaustive enums could have additional variants added in future. Therefore, when matching against variants of non-exhaustive enums, an extra wildcard arm must be added to account for any future variants.

UnknownFile

The verification covers a file the set does not describe.

Fields

file_id: FileId

DuplicateFile

Two entries in the verification claim the same file.

Fields

file_id: FileId

UncoveredFile

A recoverable file in the set has no entry in the verification. A carry must describe the whole set: what it does not mention would otherwise be silently taken as unrecoverable.

Fields

file_id: FileId

SliceCountMismatch

The per-slice validity vector is not the length the set’s slice layout requires for that file.

Fields

file_id: FileId

expected: usize

supplied: usize

DamagedCountMismatch

missing_slice_count disagrees with the count of invalid slices, or a Damaged(n) status disagrees with either.

Fields

file_id: FileId

declared: u32

actual: u32

IncompleteCompleteFile

A file claimed Complete whose validity vector is not all-valid.

Fields

file_id: FileId

MissingFileWithContent

A file claimed Missing for which a stat fingerprint was supplied, or whose validity vector claims a valid slice. A missing file has neither.

Fields

file_id: FileId

UnfingerprintedFile

A file that is not Missing but carries no stat fingerprint. Without one there is nothing for the carry gate to re-check, so the carry would be refused at repair time anyway; refusing to build it says so up front.

Fields

file_id: FileId

RelocatedFile

A Renamed status. A carry built from a host verification describes files at their canonical paths only (see ScanCarry::from_verification).

Fields

file_id: FileId

Set(Par2Error)

The set could not be laid out into source files and blocks at all.

Trait Implementations

impl Debug for ExternalCarryError

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Display for ExternalCarryError

fn fmt(&self, __formatter: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Error for ExternalCarryError

fn source(&self) -> Option<&(dyn Error + 'static)>

Returns the lower-level source of this error, if any.

fn description(&self) -> &str

👎Deprecated since 1.42.0:

use the Display impl or to_string()

fn cause(&self) -> Option<&dyn Error>

👎Deprecated since 1.33.0:

replaced by Error::source, which can support downcasting

fn provide<'a>(&'a self, request: &mut Request<'a>)

🔬This is a nightly-only experimental API. (error_generic_member_access)

Provides type-based access to context intended for error reports.

impl From<Par2Error> for ExternalCarryError

fn from(source: Par2Error) -> Self

Converts to this type from the input type.