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

MGS8002: ambiguous output ref prefix

magus query output <ref> accepts a unique prefix of a reference id, the same way git accepts a short commit hash. This code fires when the prefix you gave matches more than one stored ref, so the lookup is ambiguous.

Resolution

Add more characters until the prefix is unique. The error lists the matching refs; copy one in full. Full reference ids are printed on each target's result line when it runs.

MGS8002output refsqueryprefixambiguous
Last updated (b022d75e)
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.

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). Op 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.