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

graph-pipe

An advisory by default: it explains, and blocks nothing, on a read-only graph verb piped into a text filter, when magus projects the record itself.

What it catches

A read-only graph verb piped into a text filter, when magus projects the record itself.

Why

The same answer output-pipe gives, offered rather than imposed: -o name for ids, -o json for the whole record, -o template='{{.field}}' for one field. It advises on refs, query, explain and describe because they change nothing and their pipe loses no failure. A reader refused on these verbs tends to go back to grep -rn, which answers with less than the graph read it was denied.

Default and override

By default this rule takes the decision advise. A workspace sets it by name, in its root magusfile, to deny, advise or off:

magus\guard.builtins({"graph-pipe": "deny"})

A loosening takes effect once it is committed; a tightening applies at once.

Seeing it

A verdict names its rule in brackets, which is how you got here:

advise [graph-pipe]: ...

magus describe rule graph-pipe prints the same entry at a terminal, and magus describe rules lists every rule this workspace enforces.

See also

ReferencePages in this section. chained-run: magus runs sequenced with `&&` or `;`, which a pipe of the same stages runs ordered and fail-fastAn advisory by default: it explains, and blocks nothing, on magus runs sequenced with `&&` or `;`, which a pipe of the same stages runs ordered and fail-fast. output-pipe: magus output piped into a filter, when magus projects the record itselfAn advisory by default: it explains, and blocks nothing, on magus output piped into a filter, when magus projects the record itself. process-poll: a process table inspected to wait on magus work the lock already reportsAn advisory by default: it explains, and blocks nothing, on a process table inspected to wait on magus work the lock already reports.
guardrulesgraph-pipeadvise
Last updated (1a76274f)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. See workspace.

Magusfile

The magusfile.buzz that declares a project's targets (as export funs) and binds its spells. See targets.

Buzz

The language magusfiles are written in (the .buzz engine). See engines.

CI

An ordinary magusfile-defined target you compose yourself with magus\needs: magus does not hardcode its stages. Magus.RunCI treats it specially only in that it strips the rw charm, it is the anchor magus affected ci keys off, and a selected scope with no project declaring it is a load error rather than a silent no-op. See targets.

Advisor

One read-only check from the advice suite: it reads the changeset through magus and writes one titled section of findings. The same advisors run as a pull request comment in CI and inside magus diff --impact locally.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.