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

MGS3017: workspace still loading

The server holds this workspace in state LOADING: it is evaluating the workspace's magusfiles. A call that needs the loaded workspace answers UNAVAILABLE with this code and a google.rpc.RetryInfo detail naming how long to wait.

[MGS3017] workspace /repo is still loading; retry shortly

Why

A load is transient, so the call is safe to retry unchanged. This is the twin of MGS3016: that one needs a person to fix a source first, this one needs only time. A load most often runs here after a source change reloads a workspace that had failed.

Resolution

Retry after the retry_delay in RetryInfo. If the retry answers MGS3016, the load finished and failed; follow that page.

sandbox diagnosticsLanding page for the sandbox that confines magus spells to the workspace, plus its MGS2xxx diagnostics for denied reads, writes, execs, and env leaks. MGS3016: workspace failed to loadThe server refused a call because the workspace it targets failed to load, usually a magusfile that does not compile. The server holds the failure until a workspace source changes. Console APILoopback JSON API the console reads your live workspace through - the graph, insight, diff, run-output, plan and ledger routes. Loopback only, bearer token, GET except where named. Mutation sits on a few bounded surfaces beside it, none of which touches your working tree. FAQShort answers to the questions that come up first with magus - spells versus targets versus charms, why runs are read-only, how the cache decides, affected builds, the broker and the server, and adding a tool.
MGS3017serverworkspaceconsolemcpUNAVAILABLEretry
Last updated (95680f58)
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.

Magusfile

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

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.

Server

The background process a person starts with magus server start. It serves MCP, the console, background jobs and the warm knowledge graph, and adopts nested magus calls into one pool. See server.

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.

Conventions

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