Errors

The codes commands answer with beside their own, each set laid out once. A command's page names the sets it inherits.

Defined here

toolchain:toolchain

CodeMeaningRemedy
STORE_SETTING_NOT_HONOUREDThe toolchain's configuration states a store of its own to read, and an installed toolchain reads the published catalog and no other store.Remove the setting the message names from the configuration.

toolchain:toolchain-release

CodeMeaningRemedy
APPLICATION_NAME_INVALIDThe text given does not name an application as one is written.Write the application's name, such as dev-tool, with @<major>.<minor>.<patch> after it for one release, such as dev-tool@1.2.0.
APPLICATION_NOT_FOUNDThe catalog holds no release of an application of that name.Check the name against the applications the catalog publishes.
VERSION_NOT_RELEASEDThe catalog holds releases of the application, but none of the version asked for built for this machine's platform; the message lists the versions it holds.Ask for one of the versions the message lists, or for none to take the newest.
PLATFORM_NOT_BUILTThe catalog holds no release of the application built for this machine's platform -- none at all, or none of the version asked for.Install on a platform the application is released for; the message names the platforms it is built for where there are any.
RELEASE_FILE_MISSINGThe catalog lists the release but holds no file for it.Report it against the catalog; nothing on this machine repairs it.
RELEASE_DIGEST_UNRECORDEDThe catalog records no digest for the release, so what it holds cannot be checked and is not used.Report it against the catalog; nothing on this machine repairs it.
RELEASE_DIGEST_MISMATCHThe file the catalog holds for the release is not the one that was released -- its digest differs from the one recorded -- so it is not used.Run the command again, in case the download was damaged; if it fails the same way, report it against the catalog.
RELEASE_NOT_UNPACKEDThe release was obtained and checked, but could not be unpacked into place; the message says why.Repair what the message names -- most often space or permission on the install directory -- and run the command again.
RELEASE_HOLDS_NO_EXECUTABLEThe release unpacked holds no executable named for the application, so there is nothing to run.Report it against the release; install another version meanwhile.
APPLICATION_IN_USEThe installed version could not be replaced because a running copy of the application holds its files.Close every running copy of the application and run the command again.
TOKEN_MALFORMEDThe distribution token given, kept for this user or stated in SOLIDPLANS_TOKEN is not shaped as one -- sps_pkg_ and 43 letters, digits, - or _ -- so it is not sent; the message says where it was read from.Copy the token again from where it was issued, and set it with toolchain token set or in SOLIDPLANS_TOKEN.
TOKEN_UNREADABLEA distribution token is kept for this user, and its file could not be read; the message names the file and why.Repair what the message names -- most often permission on the file -- or set the token again with toolchain token set.
TOKEN_MISSINGThe product's catalog answers only to a distribution token, and none was sent -- none is kept for this user and none is stated in SOLIDPLANS_TOKEN.Set the token issued to you with toolchain token set, or state it in SOLIDPLANS_TOKEN.
TOKEN_UNKNOWNThe distribution token sent is not one the product's catalog knows; the message says where it was read from.Check it is the token issued to you, copied whole, and set it again; if it is, ask for a new one.
TOKEN_REVOKEDThe distribution token sent has been revoked, so the product's catalog no longer answers to it.Ask for a new token, and set it with toolchain token set or state it in SOLIDPLANS_TOKEN.
TOKEN_EXPIREDThe distribution token sent has expired, so the product's catalog no longer answers to it. Every command that fetches warns of this in the fortnight before it happens.Ask for a new token, and set it with toolchain token set or state it in SOLIDPLANS_TOKEN.
TOKEN_NOT_ENTITLEDThe distribution token sent is good, and does not cover the application or library that was asked for.Ask whoever issued the token for one that covers it.

Referenced

The error sets its commands inherit that another unit defines.

Error setCodes
pkgmgr:pkgmgr-store32

cli:cli

CodeMeaningRemedy
REPO_ROOT_VALIDATION_FAILEDThe repository root the run was given, by --repo-root or by the directory it was started in, is not a directory that can be acted on.Run the command from inside the repository, or pass --repo-root naming its root.
RUNTIME_CONFIG_FAILEDA runtime configuration file the run reads -- the application's cli.config.yml at one of its scopes -- does not load, or sets an argument default a scope may not set.Correct the file the message names; config init writes one that loads.
COMMAND_CONFIG_FAILEDThe configuration the command itself is declared by does not load, so the command cannot be run. This is a fault in the application as it was built, not in anything the person running it supplied.Report it against the application's release, with the message; reinstalling the release with update --force replaces a damaged copy.
MANIFEST_VALIDATION_FAILEDThe command reads the repository's manifest.yml, and none was found at the root, or the one found does not load.Run the command in a repository that has a manifest, pass --manifest naming one, or correct the manifest where the message says it does not load.
APP_CONFIG_FAILEDThe application's own configuration file in the repository does not load against the type the application declares for it.Correct the file the message names; config init writes one that loads.
INPUT_VALIDATION_FAILEDAn argument the command line gave is not one the command accepts once it is read -- the wrong type, a value outside its choices, or one a rule on the input refuses.Give the argument as the command's --help describes it.
OUTPUT_VALIDATION_FAILEDThe command answered with data that does not match the output it declares, so the answer was withheld. This is a fault in the command, not in how it was run.Report it against the application's release, with the command line that produced it.
PIPE_STDIN_NOT_PIPEDThe command was asked to take its input from stdin, by --from-stdin or by - as a document input's value, and nothing is piped to it -- stdin is a terminal, or there is none.Pipe in the output of a command run with --response-format json, or give the input another value.
SECRET_NOT_GIVENThe command takes a secret input, which is never typed on the command line, and nothing was typed at its prompt or piped to its standard input.Run the command at a terminal and type the value at the prompt, or pipe it to the command's standard input, one line for each secret it takes.
SECRET_STDIN_CLAIMEDThe command takes a secret input from standard input, and standard input already carries its piped inputs -- --from-stdin, or a document input given - -- so there is nothing to read the secret from.Run the command at a terminal to be asked for the secret, or give its other inputs on the command line.
PIPE_STDIN_CLAIMED_TWICE--from-stdin was given beside a document input given - or -:<path>, so the piped answer would be both the command's inputs and one of them.Keep one of the two forms.
PIPE_FIELD_NOT_FOUNDA document input given -:<path> names a field the piped answer does not hold -- a key no mapping on the way has, or an index past the end of a list or into something that is no list -- or the text after -: is no path.Name a field the command before the pipe answers with, as keys joined by . with [<n>] picking an item from a list, as releases[0].notes.
ENVELOPE_UNREADABLEWhat was piped to the command is not an envelope a command writes, so there is no answer in it to take as input.Run the command before the pipe with --response-format json, and pipe nothing else between the two.
PIPE_UPSTREAM_FAILEDThe command before the pipe refused, so there is no answer to take as input and this command did not run. Its own errors follow this one in the envelope.Repair what the errors after this one name, in the command before the pipe, and run the pipeline again.
PIPE_ANSWER_NOT_INPUTS--from-stdin takes the piped answer as the command's inputs by name, and the answer is no mapping, or carries a field the command declares no input for.Pipe in a command whose answer holds only this command's inputs, or give the answer to one document input with - instead.
UNHANDLED_EXCEPTIONThe command failed in a way nothing anticipated, and the message is the failure's own text.Report it against the application's release, with the command line and the message.
APPLICATION_RELEASE_NAME_UNKNOWNThe application could not tell which release it is -- the project it was released with, or which of that project's applications it is -- so it cannot look its releases up.Run the application as it was installed, from the directory toolchain install placed it in, or report it against the release.