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

MGS3040: a job check its worker cannot run

magus job fork, magus job apply and magus\job.put refused a job record whose check its worker could never run to a passing record:

[MGS3040] check.target "tset" is not a target of project ".": name one
  `magus describe targets` lists

Nothing was written to the job store.

What fires it

  • A check naming a project or a target the workspace does not have.
  • A check the guard would deny the worker, including one only the lease gate lets through.
  • A check only a person may run.
  • A check whose arguments narrow away the tests of the packages the job writes, such as a -run that matches none of them.

Why

The check is the evidence the job is accepted on. A check the worker cannot run leaves it with no way to finish, and the refusal comes after the work is done.

What to do

Name a target the workspace has, in the project the job writes, with arguments that still run the tests of the packages it changes. magus describe targets lists the targets.

See also

  • Leases: the check and how a worker is graded.
MGS3040jobsleasesforkapplyagentsvalidationcheck
Last updated (29d8b3de)
Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. Workspace in full.

Project

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

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.

Agent

A model working through an agent host such as Claude Code, Codex, Cursor or OpenCode. magus treats an agent as one more caller of its CLI, MCP tools and console, held to the same checks as a person. Agent in full.

Job

The unit of delegated work, and one row of the job store: what an orchestrating agent handed out, with its goal, the checkpoint it was cut against, the paths it may write or must not touch, and the one check it runs. A job's holder is either a session, for work an orchestrator handed out, or the daemon, for its own maintenance. The store records; the agent guard is what reads those facts back when grading a write. Job 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.

Lease

The grant a holder takes on a job: the write and read paths that job declared, enforced in the checkout that took it with magus job exec. A job is the piece of work; a lease is permission over it. Lease in full.

Conventions

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