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

MGS9029: review host failed

The server answered 502 bad gateway because the review host did not take a publish or a reply. Nothing was sent.

[MGS9029] publish: no pull request is open for this branch
  see: .../MGS9029.md

Why

Publish and reply put sentences in front of colleagues, so they fail loudly: a reader told a send succeeded when it did not will never find out. The message carries the host's own reason after the op name (no open review, no credential, an HTTP status from the host).

Resolution

Act on the reason it names, then send again. The drafts stay in the session until they are published.

What this is not

  • Not an incomplete request. A reply with no thread or no text is MGS9023, answered 400 because the fix is on the caller's side.
  • Not a review lookup. Reading the open review never fails; an unreachable host is a closed target with a reason.
MGS9029apireviewpublish502
Last updated (8b20a199)
Earlier changes on this page (1)

Full history ↗ · Blame source ↗

Glossary

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.

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.

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.

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.

Conventions

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