ErrLookup › rust-lang/cargo

rust-lang/cargo

The Rust package manager · Rust · 349 source files

Analyzed at 0e07a15537 on 2026-08-06. 313 documented errors.

Code / MessageTypeSeverityTags
not implemented
panic critical cargo, nightly, features, unstable, panic, resolver
argument for --color must be auto, always, or never, but fou
validation error cargo, cli, color, argument-parsing, cargo-util-terminal
no executable for `{}` found in PATH
exception error cargo, path, executable, environment, cargo-util
path at `{}` was not valid utf-8
exception error io, utf-8, encoding, files, cargo-util
failed to parse process output: {}
exception error process, io, parsing, build, cargo-util
subcommand is required, add a subcommand to the command alia
validation error cargo, alias, config, cli
alias {} has unresolvable recursive definition: {} -> {}
validation error cargo, alias, config, recursion, cli
invalid character `+` in dependency name: `+{toolchain}`
validation error cargo, add, toolchain, cli, argument-parsing
feature `{feature}` must be qualified by the dependency it's
validation error cargo, add, features, cli
feature `{feature}` is not allowed to use explicit `dep:` sy
validation error cargo, add, features, cli
`{feature}` is unsupported when inferring the crate name, us
validation error cargo, add, features, git, path, cli
multiple slashes in feature `{feature}` is not allowed
validation error cargo, add, features, cli
cannot specify multiple crates with `--rename`
validation error cargo, add, rename, cli
invalid character `+` in package name: `+{toolchain}` Us
validation error cargo, install, toolchain, cli, argument-parsing
invalid package name: `{url}` Use `cargo install --git {
validation error cargo, install, git, url, cli
missing crate name before '@'
validation error cargo, install, version, cli, argument-parsing
crate name is empty
validation error cargo, install, validation, cli
cannot specify both `@<VERSION>` and `--version <VERSION>`
validation error cargo, install, version, cli
`cargo run` does not support glob pattern `{}` on package se
validation error cargo, run, packages, glob, cli
running the file `{cmd}` requires `-Zscript`
validation error cargo, run, script, nightly, unstable, cli
no such file or subcommand `{cmd}`{is_dir}{suggested_command
validation error cargo, cli, subcommand, script, unstable
no such subcommand `{cmd}`{suggested_command}{suggested_scri
validation error cargo, cli, subcommand, typo
{}
validation error cargo, tree, cli, argument
`--edges public` requires `-Zunstable-options`
validation error cargo, tree, unstable, nightly, argument
"--package <SPEC>" requires a SPEC format value. Run `cargo
validation error cargo, uninstall, cli, argument, package-spec
invalid character `+` in package name: `+{toolchain}` Us
validation error cargo, update, toolchain, rustup, cli
cannot specify both `@{v}` and `--version`
validation error cargo, yank, publish, cli, argument
missing crate name for `@{v}`
validation error cargo, yank, publish, cli, argument
subcommand is required, but `{alias_name}` is empty
validation error cargo, alias, config, cli
dependency `{}` in package `{}` requires a `{}` artifact to
exception error cargo, artifact, dependency, manifest, target
jobs may not be 0
validation error cargo, build, parallelism, config, argument
could not parse `{j}`. Number of parallel jobs should be `de
validation error cargo, build, parallelism, config, argument
malformed output when learning about crate-type {} informati
exception error cargo, build, rustc, toolchain, wrapper
output of --print={request} missing when learning about targ
exception error cargo, build, rustc, cross-compile, toolchain, target
cannot produce {} for `{}` as the target `{}` does not suppo
exception error cargo, build, crate-type, cross-compile, target
cannot compile `{}` as the target `{}` does not support any
exception error cargo, build, crate-type, cross-compile, target
could not find specification for target `{target}`. Depend
exception error cargo, build, cross-compile, toolchain, target
several matching instances of `target.'cfg(..)'.runner` in c
exception error cargo, config, target, runner, cfg
several matching instances of `target.'cfg(..)'.linker` in c
exception error cargo, config, target, linker, cfg
build script logged errors
exception error build-script, custom-build, stdout, structured-error
multiple packages link to native library `{}`, but a native
exception error links, native-library, dependency-graph, manifest
parsing `{}` requires `-Zscript`
validation error script, unstable, nightly, embedded-manifest, rustc
{} --toolchain {}
exception error build-std, rust-src, rustup, sysroot, unstable
{:?} does not exist, unable to build with the standard libra
exception error build-std, rust-src, sysroot, unstable
failed to merge config value from `{}` into `{}`: expected {
exception error config, merge, config-value, type-mismatch
{key:?} could not be found in the environment snapshot
exception error environment, env-snapshot, config
`{}` expected {}, but found a {}
exception error config, type-mismatch, deserialization, config-value
missing config key `{}`
exception error config, missing-key, deserialization
failed to connect to jobserver from environment variable `{n
exception warning jobserver, make, environment, parallelism
Cargo couldn't find your home directory. This probably means
exception error environment, home-directory, cargo-home, config
$CARGO not set
exception error environment, cargo-exe, self-invoke, subcommand
no argv[0]
exception error environment, cargo-exe, argv, process
unexpected variable `{variable}` in build.build-dir path `{r
exception error config, build-dir, template, path
unexpected {btype} bracket `{literal}` in build.build-dir pa
exception error config, build-dir, template, syntax, path
invalid configuration for key `{}` {}
exception error config, type-mismatch, config-value
the -Zhost-config flag requires the -Ztarget-applies-to-host
validation error unstable, nightly, host-config, target, config
`{}` is not supported in build script overrides
validation error config, target, build-script, links-overrides, unsupported-key
Deprecated dependency sections are unsupported: {}
validation error cargo-add, manifest, deprecation, toml
cannot add `{}` as a dependency to itself
validation error cargo-add, self-dependency, path, cycle
unrecognized feature{} for crate {}: {}
validation error cargo-add, features, typo, version-mismatch
the manifest file {} needs to be updated but {locked_flag} w
exception error cargo-add, locked, ci, manifest
cannot specify a git URL (`{url}`) with a version (`{v}`).
validation error cargo-add, git, version, conflict
cannot specify a path (`{raw_path}`) with a version (`{v}`).
validation error cargo-add, path, version, conflict
dependency name is required
validation error cargo-add, validation, missing-argument
dependency ({}) specified without providing a local path, Gi
validation error cargo-add, workspace, inheritance, missing-source
cannot override workspace dependency with `--default-feature
validation error cargo-add, workspace, inheritance, default-features
cannot override workspace dependency with `--registry`, eith
validation error cargo-add, workspace, inheritance, registry
cannot override workspace dependency with `--rename`, either
validation error cargo-add, workspace, inheritance, rename
all versions of crate `{dependency}` are too new per `min-pu
exception error cargo-add, supply-chain, policy, publish-age
the crate `{dependency}` could not be found at `{source}`
exception error cargo-add, path, git, not-found
unexpectedly found multiple copies of crate `{dependency}` a
exception error cargo-add, path, git, ambiguous
multiple packages found at `{src}`: {} To disambiguate,
exception error cargo-add, git, disambiguation, workspace
cannot clean `{}`: not a directory
exception error cargo-clean, filesystem, safety, target-dir
cannot clean `{}`: {err}
exception error cargo-clean, target-dir, validation, safety
failed to open `{}`: {}
exception error cargo-clean, io, permissions, filesystem
package ID specification `{}` did not match any packages{}
exception error cargo-clean, package-spec, not-found, typo
warnings are denied by `build.warnings` configuration
exception error cargo-build, warnings, lint, config
package `{}` cannot be tested because it requires dev-depend
validation error cargo, workspace, dev-dependencies, testing, manifest
extra arguments to `{}` can only be passed to one target, co
validation error cargo, rustc-args, compilation, cli, target-selection
could not compile due to {error_count} previous target resol
exception error cargo, manifest, target-path, compilation, validation
crate types to rustc can only be passed to one target, consi
validation error cargo, rustc-args, crate-type, target-selection, compilation
crate types can only be specified for libraries and example
validation error cargo, crate-type, manifest, compilation, target-selection
--exclude can only be used together with --workspace
validation error cargo, cli, workspace, package-selection, flags
{}package(s) `{}` not found in workspace `{}`
exception error cargo, workspace, package-selection, cli, manifest
{}package pattern(s) `{}` not found in workspace `{}`
exception error cargo, workspace, package-selection, glob, cli
no {target_desc} target {named} `{target_name}`{unmatched_pa
exception error cargo, target-selection, cli, did-you-mean, manifest
no library targets found in package `{}`
exception error cargo, library, manifest, target-selection, compilation
no library targets found in packages: {}
exception error cargo, library, workspace, manifest, target-selection
invalid feature `{}` in required-features of target `{}`: `d
validation error cargo, manifest, features, required-features, dependencies
invalid feature `{}` in required-features of target `{}`: op
validation error cargo, manifest, features, required-features, weak-deps
target `{}` in package `{}` requires the features: {} Consid
validation error cargo, features, required-features, target-selection, compilation
cannot open specified crate's documentation: no documentatio
exception error cargo, documentation, rustdoc, cli, doc
warnings are denied by `build.warnings` configuration
exception error cargo, fetch, warnings, config, lint, dependencies
expected rustc or `@path` as first argument
exception error cargo, cargo-fix, proxy, rustc, internal
expected rustc as first argument
exception error cargo, cargo-fix, proxy, argfile, rustc, internal
could not find .rs file in rustc args
exception error cargo, cargo-fix, proxy, source-file, rustc, internal
metadata version {} not supported, only {} is currently supp
validation error cargo, metadata, versioning, cli, api
unknown vcs specification: `{}`
validation error cargo-new, vcs, config, cli-args
can't specify both lib and binary outputs
validation error cargo-new, cli-args, validation
{err}{help}
validation error cargo-new, package-name, validation, naming
invalid package name `{}`: it is a Rust keyword{}
validation error cargo-new, package-name, rust-keyword, naming
invalid package name `{}`: it conflicts with cargo's build d
validation error cargo-new, package-name, build-artifacts, naming
invalid package name `test`: it conflicts with Rust's built-
validation error cargo-new, package-name, std-library, naming
invalid package name `{}`: it is a reserved Windows filename
validation error cargo-new, package-name, windows, reserved-filename, portability
multiple possible binary sources found: {} {} cannot aut
validation error cargo-init, binary-target, ambiguity, source-detection
cannot have a package with multiple libraries, found both `{
validation error cargo-init, library-target, ambiguity, source-detection
destination `{}` already exists Use `cargo init` to initial
validation error cargo-new, filesystem, destination, cli-usage
cannot create package in the home directory help: use `carg
validation error cargo-init, filesystem, home-directory, safety
`cargo init` cannot be run on existing Cargo packages help:
validation error cargo-init, manifest, filesystem, cli-usage
more than one of .hg, .git, .pijul, .fossil configurations f
validation error cargo-init, vcs, detection, ambiguity
Character at line {} is invalid. Cargo only supports UTF-8.
exception error vcs, encoding, utf-8, ignore-file
{err}
exception error vcs, io, ignore-file, filesystem
invalid inclusion of reserved file name {} in package source
validation error cargo-package, reserved-filename, packaging, metadata
{manifest_key_name} `{}` does not appear to exist{}.
exception error cargo-package, manifest, readme, license-file, validation
{}This may cause issue during packaging, as modules resoluti
exception error cargo-package, build-script, manifest, packaging, portability
path does not have a unicode filename which may not unpack o
validation error cargo-package, unicode, filesystem, portability, encoding
cannot package a filename with a special character `{}`: {}
validation error packaging, cross-platform, windows, filenames, publish
{} files in the working directory contain changes that were
exception error packaging, vcs, git, publish, dirty
Source directory was modified by build.rs during cargo publi
exception error packaging, publish, build-scripts, verify, determinism
a Cargo.lock must exist for this command
exception error lockfile, pkgid, resolve
found a virtual manifest at `{}` instead of a package manife
exception error manifest, workspace, virtual-manifest, packaging, publish
no sessions found{context}
exception error report, build-analysis, experimental, nightly
no sessions found{context}
exception error report, build-analysis, experimental, sessions, nightly
no sessions found{context}
exception error report, timings, build-analysis, experimental, nightly
no timing data found in log
exception error report, timings, build-analysis, corrupted-log
`cargo run` does not support glob patterns on target selecti
validation error run, target-selection, glob
a bin target must be available for `cargo run`
validation error run, targets, binary, manifest
example target `{}` is a library and cannot be executed
validation error run, examples, targets, crate-type
`cargo run` could not determine which binary to run. Use the
validation error run, targets, ambiguity, binary, manifest
`cargo run` can run at most one executable, but multiple wer
validation error run, targets, binary
cannot specify both recursive and precise simultaneously
validation error update, lockfile, cli, flags
you can't generate a lockfile for an empty workspace.
validation error update, workspace, lockfile, manifest
package ID specification{plural} did not match any direct de
exception error update, dependencies, breaking, lockfile
cannot {action} the lock file {lockfile_path} because {locke
exception error lockfile, locked, frozen, ci, offline
lock file version `{current_version:?}` requires `-Znext-loc
exception error lockfile, version, nightly, toolchain
all dependencies must have a version requirement specified w
validation error packaging, publish, dependencies, manifest, version
could not find `{}` in registry `{}`
exception error registry, package-resolution, cargo-info, lookup
the replacement specification `{}` matched multiple packages
exception error replace, dependency-resolution, config, deprecated
replacement specification `{}` matched {} and tried to overr
exception error replace, dependency-resolution, version-mismatch
overlapping replacement specifications found: * {} * {}
exception error replace, dependency-resolution, config, duplicate
lock file version `{n}` requires `-Znext-lockfile-bump`
exception error lockfile, nightly, version, toolchain
package `{}` is specified twice in the lockfile
exception error lockfile, duplicate, corruption, merge
cyclic package dependency: package `{id}` depends on itself.
exception error dependency, cycle, graph, workspace
package collision in the lockfile: packages {} and {} are di
exception error lockfile, collision, path-dependency, workspace
checksum for `{}` was not previously calculated, but a check
exception error checksum, lockfile, source-replacement, integrity
checksum for `{}` could not be calculated, but a checksum is
exception error checksum, lockfile, source-replacement, integrity
checksum for `{}` changed between lock files this could be
exception critical checksum, lockfile, integrity, mirror, security
the crate `{}` depends on crate `{}` multiple times with dif
exception error dependency, naming, manifest, duplicate
`resolver` setting `{}` is not valid, valid options are "1",
validation error manifest, config, resolver, validation
failed to find entry for `{}` in directory source
exception error directory-source, vendor, path, missing
the listed checksum of `{}` has changed: expected: {} actual
exception error directory-source, vendor, checksum, integrity
error: failed to validate host key: {:#}
exception error ssh, git, host-key, known-hosts, security
error: unknown SSH host key The SSH host key for `{hostname}
exception error ssh, git, host-key, known-hosts, security, first-connect
error: SSH host key has changed for `{hostname}` ***********
exception critical ssh, git, security, host-key, mitm, known-hosts
error: Key has been revoked for `{hostname}` ***************
exception critical ssh, git, security, revoked-key, host-key, compromise
error: Found a `@cert-authority` marker for `{hostname}` Ca
exception error ssh, git, cert-authority, security, enterprise, config
can't checkout from '{}': you are in the offline mode ({offl
exception error cargo, git, offline, network, config
attempting to update a git repository, but {offline_flag} wa
exception error cargo, git, offline, network
no path segments on url
validation info cargo, git, github-fast-path, url, internal
couldn't find username
validation info cargo, git, github-fast-path, url, internal
couldn't find repository name
validation info cargo, git, github-fast-path, url, internal
too many segments on URL
validation info cargo, git, github-fast-path, url, internal
failed to verify the checksum of `{}`
exception error cargo, registry, checksum, download, security, network
path `{}` is not a blob in the git repo
exception error cargo, registry, git-index, validation
config.json not found
exception error cargo, registry, sparse, config, network
non UTF8 path: {}
exception error cargo, registry, sparse, utf8, internal
sparse registry url must end in a slash `/`: {url}
validation error cargo, registry, sparse, url, config
cache expected 4 bytes for index schema version
exception error cargo, registry, cache, corruption, validation
registry said cache valid when no cache exists
exception error cargo, registry, cache, validation, internal
local registry path is not a directory: {}
validation error cargo, registry, local-registry, config, filesystem
local registry index path is not a directory: {}
validation error cargo, registry, local-registry, config, filesystem
failed to verify the checksum of `{}`
exception error cargo, registry, local-registry, checksum, security
unable to read .cargo-ok file at {path:?}: {e}
exception error cargo, registry, filesystem, permissions, io
invalid tarball downloaded, contains a file at {entry_path:?
exception critical cargo, registry, tarball, security, path-traversal, validation
invalid tarball downloaded, contains an entry at {entry_path
exception critical cargo, registry, tarball, security, symlink, validation
multiple registries are configured with the same index url '
validation error cargo, registry, auth, config, validation
no credential providers could handle the request
exception error authentication, credentials, registry, network
invalid url `{}`: cannot-be-a-base-URLs are not supported
validation error url, canonicalization, git, validation
"--package <SPEC>" requires a SPEC format value, which can b
validation error cli, package-selection, argument-parsing
glob patterns on package selection are not supported.
validation error cli, package-selection, glob, validation
manifest path `{}` does not exist
validation error cli, manifest, filesystem, path
manifest path `{}` is a directory but expected a file{sugges
validation error cli, manifest, filesystem, path
the manifest-path must be a path to a Cargo.toml or script f
validation error cli, manifest, script, unstable, path
the manifest-path must be a path to a Cargo.toml file: `{}`
validation error cli, manifest, script, path
embedded manifest `{}` requires `-Zscript`
validation error cli, manifest, script, unstable, path
credential process `{}` failed with status {}`
exception error authentication, credentials, external-process, config
could not find `{}` in `{}` or any parent directory, but fou
validation error filesystem, manifest, case-sensitivity, path
could not find `{}` in `{}` or any parent directory
validation error filesystem, manifest, path, workspace
Could not find `{}` in `{}`
validation error filesystem, manifest, workspace, path
expect run ID in format `20060724T012128000Z-<16-char-hex>`,
validation error run-id, parsing, logger, validation
{}: {:?}
exception error rustc, utf8, encoding, toolchain, wrapper
probably rustup rustc, but without rustup's env vars
exception error rustc, rustup, environment, toolchain, fingerprint
'{}' is not a valid artifact specifier
validation error manifest, artifact, dependency, validation, toml
Cannot specify both 'bin' and 'bin:<name>' binary artifacts,
validation error manifest, artifact, dependency, validation, toml
Found {} duplicate binary artifact{}
validation error cli, build-artifacts, validation
`{key}.workspace = false` is unsupported
validation error manifest, dependencies, workspace
dependency ({key}) specified without providing a local path,
validation error manifest, dependencies, validation
Use of `default_features` in `{key}` is unsupported, please
validation error manifest, dependencies, naming
Unrecognized` dependency entry format for `{key}`
validation error manifest, dependencies, toml
can only edit absolute paths, got {}
validation error api, paths, editor
-Zfix-edition expected a value
validation error cli, unstable, features
manifest is missing either a `[package]` or a `[workspace]`
validation error manifest, parser, validation
parsing `{}` requires `-Zscript`
validation error unstable, embedded-manifest, script
failed to find a workspace root
exception error workspace, inheritance, parser
cannot override `workspace.lints` in `lints`, either remove
validation error manifest, lints, workspace
`default-features = false` cannot override workspace's `defa
validation error manifest, dependencies, edition-2024, workspace
`[project]` is not supported as of the 2024 Edition, please
validation error manifest, edition-2024, deprecation
{fields} {are} not allowed in embedded manifests
validation error embedded-manifest, manifest, script
replacements must specify a version to replace, but `{}` doe
validation error manifest, replace, dependencies
dependency ({name_in_toml}) specified without providing a lo
validation error manifest, dependencies, parser
`lints.{tool}.{name}` is not valid lint name; try `lints.{pr
validation error manifest, lints, naming
`lints.{tool}.{name}` is not a valid lint name
validation error manifest, lints, naming
`{old_path}` is unsupported as of the 2024 edition; instead
validation error manifest, edition-2024, deprecation, naming
cannot publish with `open-namespaces`
validation error
cannot specify both `metabuild` and `build`
validation error
metabuild package `{}` must be specified in `build-dependenc
validation error
can't find library `{name}`, rename file to `src/lib.rs` or
validation error
library `{}` cannot set the crate type of both `dylib` and `
validation error
cannot mix `proc-macro` crate type with others
validation error
found duplicate {target_kind} name {name}, but all {target_k
validation error
found build scripts with duplicate file stems, but all build
validation error
invalid `package.build` file name
validation error
library target names cannot contain hyphens: {}
validation error
the binary target name `{name}` is forbidden, it conflicts w
validation error
{} target names cannot be empty
validation error
{} target {}.name is required
validation error
patch for `{}` points to the same source, but patches must p
validation error
several `[patch]` entries resolving to same version `{} v{}`
validation error
override found but no real ones
validation error
found patches and a path override
validation error
found an override with a non-locked list
validation error
patch for `{}` in `{}` resolved to more than one candidate n
validation error
patch location `{}` does not contain packages matching `{}`
validation error
patch `{}` version mismatch note: patch location contains {}
validation error cargo, patch, dependency, version-mismatch, manifest
unsupported registry protocol `{unknown}` (defined in {})
validation error cargo, config, registry, crates-io, protocol
single file packages cannot be used as dependencies
validation error cargo, dependency, path, manifest
unexpected variable `{variable}` in resolver.lockfile-path `
validation error cargo, config, lockfile, resolver, template
unexpected {btype} bracket `{literal}` in build.build-dir pa
validation error cargo, config, lockfile, template, syntax
`{}` was defined in {} but could not be resolved with {}
exception error cargo, path, workspace, relative-path
`{}` resolved to non-UTF value (`{}`)
exception error cargo, path, utf8, filesystem, encoding
argument for argfile contains invalid UTF-8 characters: `{}`
exception error cargo, process, argfile, utf8, cli
argument for argfile contains newlines: `{arg}`
exception error cargo, process, argfile, newline, cli
could not find cargo home dir
exception error cargo, environment, home, cargo-home, container
could not find rustup home dir
exception error cargo, rustup, environment, home, container
missing field `{}`
validation error cargo, config, serde, deserialization, manifest
see above
exception error cargo, diagnostics, sentinel, output
maximum limit reached when reading
exception error cargo, io, reader, limit, download
the path was not found
exception error cargo, windows, canonicalize, path, not-found
failed to parse the version requirement `{}` for dependency
validation error cargo, dependency, semver, version, manifest
failed to read path `{path:?}`
exception warning cargo, cache, io, filesystem, permissions
failed to serialize credential provider error
panic critical cargo, credential, serde, panic, json
only none when there is 1
panic critical cargo, cargo-add, panic, invariant, internal
always at least one crate
panic critical cargo, cargo-add, panic, invariant, internal
required(true)
panic error cargo, clap, argument-parsing, internal-invariant
a file should always have a parent
panic error cargo, path-handling, manifest, internal-invariant
already loaded without errors
panic error cargo, config, shell-completion, nightly, internal-invariant
set_verify_owner_validation should never fail
panic error cargo, git2, libgit2, startup, internal-invariant
parent dir for artifacts
panic error cargo, artifact-dependencies, bindeps, path-handling, internal-invariant
artifact present
panic error cargo, artifact-dependencies, bindeps, resolver, internal-invariant
rustc load ok
panic error cargo, rustc, toolchain, sysroot, internal-invariant
artifact-dir was not locked
panic error cargo, layout, artifact-dir, docs, internal-invariant
target must support `bin`
panic error cargo, target, cross-compile, binaries, internal-invariant
must be a host tuple
panic error cargo, host-triple, toolchain, target-applies-to-host, internal-invariant
running a script not depending on an actual script
panic error cargo, build-scripts, unit-graph, metabuild, internal-invariant
has_custom_build should have RunCustomBuild
panic error cargo, build-scripts, metadata, unit-graph, internal-invariant
output must exist after running
panic error cargo, build-scripts, fingerprint, concurrency, internal-invariant
failed to find rmeta
panic error cargo, fingerprint, rmeta, pipelined, internal-invariant
artifact-dir was not locked
panic error cargo, rustdoc, fingerprint, layout, internal-invariant
failed to find rmeta dep for pipelined dep
panic error cargo, pipelined, rmeta, extern, internal-invariant
resolve should have a single spec with resolved features
panic error cargo, build-std, resolver, nightly, internal-invariant
std has a lib
panic error cargo, build-std, std, targets, internal-invariant
able to invoke rustc
panic error cargo, build-std, sysroot, rustc, toolchain, internal-invariant
artifact-dir was not locked
panic error rust, cargo, panic, invariant, timings, build-layout
artifact dep
panic error rust, cargo, panic, invariant, artifact-deps, unstable
already loaded config values
panic error rust, cargo, panic, invariant, config, cargo-vendor
env var was not array
panic error rust, cargo, panic, invariant, env-vars, unstable, toml
was not filled at beginning of the function
panic error rust, cargo, panic, invariant, credentials, once-cell, concurrency
len() == 1 above
panic error rust, cargo, panic, invariant, config, toml, cli-args
must be utf-8 in toml
panic error rust, cargo, panic, invariant, utf-8, build-target, config, locale
normalized have a path
panic warning rust, cargo, panic, invariant, lint, manifest, bin-targets
manifest validated
panic error rust, cargo, panic, invariant, cargo-add, features, manifest
latest always has a source
panic error rust, cargo, panic, invariant, cargo-add, registry, source-resolution
as `None` are compatible, we can't be here
panic error rust, cargo, panic, invariant, cargo-add, msrv, rust-version
source should be resolved before here
panic error rust, cargo, panic, invariant, cargo-add, registry, source-resolution
match ensured element is present
panic error rust, cargo, panic, invariant, cargo-add, git-source, unreachable
artifact-dir was not locked during clean
panic error rust, cargo, panic, invariant, cargo-clean, build-layout, artifact-dir
packages downloaded
panic error rust, cargo, panic, invariant, cargo-compile, package-download, registry
able to invoke rustc
panic error rust, cargo, panic, invariant, cargo-fix, rustc, sysroot, toolchain
returned early
panic warning rust, cargo, panic, invariant, cargo-fix, edition-migration, manifest
just inserted
panic warning rust, cargo, panic, invariant, cargo-fix, toml-edit, edition-migration
We've already checked that there is exactly one.
panic critical cargo, panic, invariant, resolver, fix-edition, rust
at least one iteration
panic critical cargo, panic, invariant, fix, rustfix, rust
bin is an array of tables
panic error cargo, panic, invariant, cargo-new, toml-edit, rust
package is a table
panic error cargo, panic, invariant, cargo-new, workspace, toml-edit, rust
everything was utf8
panic error cargo, panic, utf8, filesystem, cargo-package, i18n, rust
must have the unit
panic error cargo, panic, invariant, cargo-report, rebuilds, build-graph, rust
manifest path is absolute
panic error cargo, panic, invariant, cargo-update, filesystem, manifest, rust
already a valid dependency
panic error cargo, panic, invariant, cargo-update, registry, dependency, rust
local path
panic error cargo, panic, invariant, cargo-vendor, local-registry, url, filesystem, rust
venedored manifests must have packages
panic error cargo, panic, invariant, cargo-vendor, manifest, package, rust
previously normalized
panic error cargo, panic, invariant, cargo-vendor, build-script, manifest, rust
dupes must be in sync
panic error cargo, panic, invariant, cargo-install, tracking, metadata, rust
validation ensures this is a table
panic error cargo, panic, invariant, lockfile, toml, metadata, rust
remote registries must have config
panic error cargo, panic, invariant, registry, network, config, rust
source ID should have valid URLs
panic error cargo, panic, invariant, lockfile, source-id, url, resolver, rust
in the non-empty branch
panic error cargo, panic, invariant, resolver, error-reporting, features, rust
packages downloaded
panic error cargo, panic, invariant, resolver, features, download, proc-macro, rust
parent not currently active!?
panic critical cargo, panic, invariant, resolver, backtracking, conflict-cache, rust
an already used dep now pending!?
panic critical cargo, panic, invariant, resolver, backtracking, registry-query, rust
not currently active!?
panic error resolver, backtracking, debug-assertion, cargo-internal, rust
why did we save a frame that has no next?
panic error resolver, backtracking, panic, cargo-internal, rust
utf-8 home
panic error ssh, known-hosts, utf-8, filesystem, encoding, locale, rust
Lockfile path can't be root
panic error lockfile, config, paths, filesystem, workspace, rust