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

MGS9025: request conflicts with current state

The server answered 409 aborted because the request was well formed and the thing it names exists, but the request cannot apply to it as it now stands.

[MGS9025] review snapshot is stale; refresh the diff
  see: .../MGS9025.md

Why

The request was written against a state that is no longer the current one:

  • A request already closed. An attention request someone else disposed of first; the message says who and when.
  • A stale snapshot. File context asked against a diff digest the working tree has since moved past.
  • No review session attached. A review op arrived before any GET /api/v1/diff paired a session to this workspace.
  • An import figure with no symbol index. The figure would read as "nothing imports anything", so it is refused.

Retrying the same request cannot succeed until the state changes.

Resolution

Read the current state and act on that: fetch the diff again, list the attention queue, GET /api/v1/diff before the first review op, or run magus graph build for the import figure.

What this is not

  • Not a malformed request. That is MGS9023, fixed by changing the request.
  • Not a workspace that is loading. That is MGS3017 while it loads, retried after a moment.
AuthPages in this section. ChangelogEvery change to magus, newest first, in Keep a Changelog format, starting with the unreleased entries. Generated from changes/unreleased/ and releases/*.yaml. TelemetryExport magus metrics and traces to any OTLP collector you run, with head-based sampling, resource attributes, and full instrument reference. StatusServiceStatusService serves the snapshot, and streams it for a live dashboard.
MGS9025apiconflictstate409
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.

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). See operations.

Sandbox

The restricted filesystem and environment a target runs in, so builds stay reproducible and side-effect-free. See sandbox.

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.

Snapshot

A point-in-time view of live state (the pool's occupancy or a tick of exported metrics), as opposed to accumulated history. See server.

Session

An agent host's conversation, by the id the host delivers to its hooks. magus never mints one: a record with no session is unattributed, and the OS user it carries says whose account ran it.

Attention request

A durable "an agent is blocked" record, opened when a magus session notify event carries the waiting or permission outcome and held until a person disposes it. magus session attention lists what is open. Nothing closes one on its own; see doctrine.

Dispose

The human act of closing an attention request: a judgment rendered, recorded with who and why. Distinct from resolving a review thread or a merge conflict: a disposition answers a request; it does not merge anything.

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.