magus v0.3.0 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.

output-reference diagnosticsLanding page for MGS8xxx diagnostics that flag problems resolving a target-output reference id with magus query, such as a ref that aged out of the cache, an ambiguous prefix, or a malformed ref passed to a ref-only flag. The CLI in practiceThe magus subcommands you actually reach for, grouped by the question you are asking, with the quirks that are not obvious from the help text. StatusServiceStatusService serves the snapshot, and streams it for a live dashboard. Logging and verbosityWhat each verbosity level actually prints, when to reach for one over another, and what ends up in your logs that you may not want to paste into a bug report.
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. See targets.

Output reference

A short, shareable id (out1a2b3c, "ref" for short) for one target execution's captured output; it appears on each target's line, and magus query output out1a2b3c prints those exact bytes. In OpenTelemetry terms it corresponds to a span (one target execution) within its trace (the whole magus invocation). See output-refs.

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.