magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit

Output-reference diagnostics

Codes in the MGS8xxx range flag problems resolving a target-output reference id (out1a2b3c) with magus query output <ref>. Every target that runs is given a short reference id for its captured output; these codes fire when that id cannot be resolved to stored output.

Codes

  • MGS8001: the ref is well-formed but no stored output exists for it; it aged out of the cache, or the ref is mistyped.
  • MGS8002: a shortened ref prefix matches more than one stored output, so the lookup is ambiguous.
  • MGS8003: magus query output was given an argument that is not a well-formed ref<hex> id, so it cannot name a stored output.
output refsdiagnosticserror codesMGS8xxxquerycache
Last updated (895d94e4)
Earlier changes on this page (3)

Full history ↗ · Blame source ↗

Glossary

Target

A named operation (build, test, ...) you invoke with magus run <target>; it may compose a spell's tool-native operations and depend on other targets. Target in full.

Cache

The content-addressed store magus consults before running a target, so unchanged work is skipped. Cache in full.

Output reference

A short, shareable id such as out1a2b3c for one target execution's captured output; magus query output prints those exact bytes. In OpenTelemetry terms it names a span. Output reference in full.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate. Run in full.

Conventions

Placeholders

Angle brackets mark a value you replace with your own; never type the brackets:

magus run <target>
magus completion <shell>    # e.g. bash, zsh, fish

<target>, <path>, <shell>, <name> and the like are stand-ins, not literal text.