Enum ResolveError 

#[non_exhaustive]
pub enum ResolveError {
    UnknownScheme {
        uri: String,
        scheme: String,
    },
    UriParseError {
        uri: String,
        source: UriParseError,
    },
    PathNotADirectory {
        path: PathBuf,
    },
    RootEscape {
        path: PathBuf,
    },
    Io {
        path: PathBuf,
        source: Error,
    },
    PathUriHasFragmentOrQuery {
        uri: String,
    },
    Fetch {
        uri: String,
        source: FetchError,
    },
    CacheIo {
        path: PathBuf,
        source: Error,
    },
}

Errors raised by resolve_namespace and resolve_namespace_with.

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.

UnknownScheme

URI didn’t match any registered scheme. scheme is the actual missing scheme — for plain transport URIs that matches the scheme of uri, but for forge-template URIs (github:, gitlab:) it’s the expanded transport scheme (typically https). That’s what the diagnostic needs to name so the user understands which transport fetcher is missing from the registry, not just that the original URI failed.

Fields

uri: String

scheme: String

UriParseError

URI failed to parse syntactically (bad fragment, missing scheme, …). Distinct from UnknownScheme: the URI is malformed at the lex layer, not just pointed at a scheme we don’t know.

Fields

uri: String

source: UriParseError

PathNotADirectory

A path: URI pointed at a file that doesn’t exist or isn’t a directory.

Fields

path: PathBuf

RootEscape

path: URI resolved to a path that escapes the workspace root (relative paths like ../../etc/passwd). Same invariant as the include-resolver — keeps a malicious lex.toml from pointing at arbitrary system locations.

Fields

path: PathBuf

Io

path: resolution failed at the filesystem layer (permission denied, broken symlink, …).

Fields

path: PathBuf

source: Error

PathUriHasFragmentOrQuery

A path: URI carried a # fragment or ? query — those are remote-only knobs (the resolver uses them on github:/gitlab:/etc. for rev and subdir). Rejecting instead of silently stripping surfaces typos like path:dir#main (where the user almost certainly meant a remote URI).

Fields

uri: String

Fetch

A registered fetcher returned an error during the network fetch. Wraps the per-fetcher error type for context.

Fields

uri: String

source: FetchError

CacheIo

The cache directory couldn’t be created or written to. Distinct from a fetch IO error: this happens before we even call the fetcher.

Fields

path: PathBuf

source: Error

Trait Implementations

impl Debug for ResolveError

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

Formats the value using the given formatter.

impl Display for ResolveError

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

Formats the value using the given formatter.

impl Error for ResolveError

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.