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

MGS9027: internal failure

The server answered 500 internal because a step it owns failed after the request was accepted.

[MGS9027] target graph failed
  see: .../MGS9027.md

Why

The message names the step (attention, target graph, graph build, render, a diff read) and nothing else. The underlying error can carry the server's absolute paths, so it goes to the server log and never to the client.

Resolution

Read the server's log output for the line with the same step name and the request path. A failure that repeats for every request usually means the workspace state on disk is unreadable; fix that and retry.

What this is not

  • Not a bad request. A change to the request fixes MGS9023; it cannot fix this.
  • Not a missing workspace. That is MGS9026.
MGS9027apiinternal500
Last updated (8b20a199)
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.

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.

Conventions

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