ADAPTER_CARRIES_THE_CONTRACT | The adapter being published carries its own copy of the adapter contract package, which a released tool has compiled in and which would shadow it, so it is refused rather than published. | Keep the contract package out of the adapter module's root and build again. |
ADAPTER_IMPORTS_BEYOND_THE_CONTRACT | The adapter being published imports a module that no tool built to the adapter contract carries, so a released tool would fail to load it. | Stop importing the module the message names, or add it to the contract's importable lists first so a tool is built carrying it. |
ADAPTER_CHECKOUT_MANIFEST_MISSING | The adapter checkout the tree pins holds no manifest that loads, so what it publishes cannot be read. | Run git submodule update --init --recursive in the tree's root. |
ADAPTER_COMMAND_FAILED | A process the repo adapter described for this command -- the linter, the test runner, the type checker -- exited with a failure; its own output above says why. | Repair what that tool's output names and run the command again. |
ADAPTER_PATH_NOT_FOUND | A path given with --paths does not exist. | Name a file or directory that exists in the repository. |
ADAPTER_PATH_OUTSIDE_REPOSITORY | A path given with --paths resolves outside the repository the command runs in. | Name a path inside the repository, or run the command in the repository that holds it. |
ADAPTER_REPOSITORY_DECLARES_NO_SOURCE | The repository pins other repositories and its ownRoots names no directory of its own, so a run naming no path has nothing to cover without crossing into them. | Declare the repository's own directories in ownRoots in .dev-tool/config.yml, or narrow the run with --modules or --paths. |
ADAPTER_SOURCE_PATH_HOLDS_A_REPOSITORY | A directory ownRoots names holds a pinned repository's checkout, so a run naming no path would cross into it. | Name only this repository's own directories in ownRoots; --recurse runs each pinned repository's own command in its checkout. |
ADAPTER_RUNTIME_INVALID | The repo adapter could not be asked for the command's process; the message carries its error. | Vendor the adapter again with dev vendor; if it persists, report it against the adapter's release. |
REPO_ADAPTER_COMMAND_NOT_IMPLEMENTED | The repository's repo adapter has no process for this command in this language. | Declare one under repoAdapterCommands in .dev-tool/config.yml, or use an adapter that implements it. Where the adapter is a configuration document, declare the verb under commands in that document, or leave the check out of the gate with gateOmissions in .dev-tool/config.yml. |
REPO_ADAPTER_COMMAND_MALFORMED | The repo adapter described a process for this command that cannot be run as written. | Report it against the adapter's release, with the message. |
REPO_ADAPTER_COMMAND_INVALID_PAYLOAD | The repo adapter answered this command with something that is not a process to run. | Report it against the adapter's release, with the message. |
REPO_ADAPTER_COMMAND_OVERRIDE_INVALID | The command declared for this verb under repoAdapterCommands in .dev-tool/config.yml cannot be rendered for this run. | Correct the declaration the message names. |
REPO_ADAPTER_PARAMETER_UNSUPPORTED | The run asks the adapter to leave something out -- a tier, an isolation -- that the adapter's command for it takes no parameter for, so it would cover what it was asked to leave out. | Vendor an adapter implementing the current contract with dev vendor, or run without the option. |
REPO_ADAPTER_PATH_SELECTION_UNSUPPORTED | The command declared for this verb under repoAdapterCommands does not read the run's paths, so it cannot be narrowed to the selected paths or to the repository's own roots. | Run without --paths, or declare the command so that it reads the paths it is handed. |
REPO_ADAPTER_CATALOG_MISSING | The repository's repo-adapter catalog does not exist and no store it defers to is reachable, so no adapter can be resolved. | Declare the adapter catalog in the manifest's catalogs with an upstream that holds the adapter, then run dev vendor. |
REPO_ADAPTER_CATALOG_INVALID | The repository's repo-adapter catalog, or the adapter coordinate the manifest names, cannot be read. | Correct the catalog declaration or the repoAdapter coordinate the message names in the manifest. |
REPO_ADAPTER_UNAVAILABLE | No build catalog this repository reads holds a build of its repo adapter, and no store its adapter catalog defers to holds a release of it. | Inside a tree run dev build --libraries-only --recurse in the tree's root; a clone standing alone sets CATALOG_ROOT to a checkout whose catalogs hold the adapter. |
REPO_ADAPTER_VENDOR_FAILED | The repo adapter was found but could not be copied into the repository's adapter catalog; the message says why. | Repair what the message names and run dev vendor again. |
REPO_ADAPTER_CONTRACT_UNMET | The resolved repo adapter does not implement the adapter contract this dev-tool calls, or cannot say whether it serves the repository's language version. | Vendor an adapter release built for this dev-tool with dev vendor, or update dev-tool. |
REPO_ADAPTER_LANGUAGE_VERSION_UNSERVED | No release of the repo adapter is for the language version the repository states it is written for. | Release the adapter for that version, or correct the version the repository states in the language's own file. |
RUNTIME_COORDINATE_UNAVAILABLE | A module resolved at run time names no version and the manifest states none, so there is nothing to publish it under. | State a version in the manifest, or give the module's runtimeCoordinate one. |
RUNTIME_ARCHIVE_FAILED | A module resolved at run time, such as a repo adapter, could not be archived for publishing; the message names the checkout and why. | Repair what the message names -- most often untracked source under the module root -- and build again. |
BUILD_CATALOG_COORDINATE_UNAVAILABLE | The manifest states no project or no version, so the build has no coordinate to register under. | State project and version in the repository's manifest. |
LIBRARY_LOOKUP_FAILED | The build catalog lists a library but names no file for it. | Publish the library again with dev build --libraries-only in the repository that holds it. A catalog you cannot rebuild from is repaired by clearing the entry with pkgmgr pkg clear --catalog-root <catalog> --label <name> --ref-type sha and registering the file again with pkgmgr pkg register. |
BUILD_ARTIFACT_DID_NOT_ANSWER | The executable just built did not answer the check run on it within the time allowed, which is as broken as failing it. | Pass --check-arg with something the executable can answer, or set checkArg to an empty list under the build command's argDefaults to turn the check off. |
BUILD_ARTIFACT_DID_NOT_RUN | The executable just built could not be started at all. | Repair what the message names, most often a missing file or permission at the artifact's path, and build again. |
BUILD_ARTIFACT_DID_NOT_START | The executable was built but exited with a failure on the check run on it; its output is in the message. | Repair what the output names -- most often a module or file the build left out of the executable -- and build again. |
RECURSE_WITHOUT_VALIDATE | --recurse runs the validation in every pinned repository, and this run validates nothing. | Pass --validate with --recurse. |
RECURSE_REPOSITORY_FAILED | The command, run in a pinned repository's own checkout under --recurse, failed there; the message names the repository and carries its output. | Run the command in that repository to see its own refusal, and repair it there. |
RECURSE_REPOSITORY_NOT_VENDORED | A pinned repository declares libraries to obtain and has none vendored, so its own command cannot run in its checkout. | Run dev build --libraries-only --recurse and then dev vendor --recurse in the tree's root. |
AFFECTED_CHANGES_UNREADABLE | git could not be run, or failed, while reading what changed, so what the change reaches cannot be worked out. | Repair what the message names -- often a --since reference git does not know -- or run with --select all. |
AFFECTED_INPUT_WITHOUT_AFFECTED | --changed-coordinates or --since says what changed, which only a run selecting by change reads, and this run does not select by change. | Pass --select affected with them, or leave them out. |
AFFECTED_SELECTION_NARROWED | The run both says what changed (--changed-coordinates or --since) and names what to cover outright (--modules or --paths). | Pass one or the other. |
AFFECTED_RECURSE_MODE_FULL | Selecting by change works from one repository's dependency graph, and --recurse-mode full is one run over every pinned repository, whose modules that graph does not hold. | Cross with --recurse-mode isolate, or pass --select all. |
TEST_NOT_IN_A_TIER | Test files sit in no directory named for a tier the repository's testTiers declares, so no run would collect them as a tier. | Move each test the message names into a tier's directory, or declare the tier in testTiers. |
TEST_TIER_NOT_COLLECTED | What the run names holds tests only in tiers the run does not collect, so it would run nothing. | Pass --tier naming the tier, --all-tiers, or name the test files themselves, which run whatever their tier. |
TEST_TIER_SELECTION_CONFLICT | --tier names tiers to collect and --all-tiers asks for every one. | Pass one or the other. |
TEST_FILE_PATTERNS_UNAVAILABLE | Which of the repository's files are tests cannot be asked, because the repo adapter its manifest names resolves neither through its own catalogs nor through those of a repository that pins it; a fixture cannot be told from a document it publishes. | Run dev vendor in the repository the message names, so its adapter catalog holds the adapter. |
TEST_TIER_UNKNOWN | --tier names a tier the repository's testTiers does not declare. | Name one of the tiers the message lists. |
TEST_TIER_NONE_DEFAULT | The repository's testTiers marks no tier default, so a run naming none collects nothing. | Name a tier with --tier, pass --all-tiers, or mark the tier a run after an edit is owed default in testTiers. |
SCHEMA_REGISTRATION_STALE | A schema registered in the schema store is not the document its source publishes, and every reference to it resolves to the stale copy. | Run dev schema gen --force to register the current document. |
SCHEMA_VENDORED_STALE | A schema vendored into a repository is not the document its source publishes, and the library's models were unpacked beside the stale copy. | Rebuild the package that publishes it with dev build --libraries-only and run dev vendor in the repository the message names. |