@mostra/cli 0.9.0 → 0.11.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/bin.js +2 -2
- package/dist/bootstrap-BStzS_41.js +1 -0
- package/dist/{bootstrap-Dc-SQHRF.js → bootstrap-_iCl_HaO.js} +3 -2
- package/dist/bootstrap-_iCl_HaO.js.map +1 -0
- package/dist/{flush-C16w3JL8.js → flush-D648gCYs.js} +12 -3
- package/dist/flush-D648gCYs.js.map +1 -0
- package/dist/index.d.ts +1 -1
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +2 -2
- package/dist/reference/cli.md +210 -4
- package/dist/reference/diagnostics.json +171 -0
- package/dist/reference/errors/MOSTRA_ACTION_PAUSED.md +23 -0
- package/dist/reference/errors/MOSTRA_ARTIFACT_BUNDLE_INVALID.md +23 -0
- package/dist/reference/errors/MOSTRA_HOME_NETWORK_FILESYSTEM.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_CONFIG_INVALID.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_HOME_MOVING.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_HOME_SUSPENDED.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_LIMIT_REACHED.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_LOGIN_FAILED.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_NOT_OWNER_INSTANCE.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_NO_INSTANCE.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_OPERATOR_UNAVAILABLE.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_OWNER_OFFLINE.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_PAUSED_BY_OPERATOR.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_QUEUE_FULL.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_RATE_LIMITED.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_SIGN_IN_REQUIRED.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_UNDER_REVIEW.md +23 -0
- package/dist/reference/errors/MOSTRA_REMOTE_UNREACHABLE.md +23 -0
- package/dist/reference/errors/MOSTRA_SUBMIT_PAUSED.md +23 -0
- package/dist/reference/self-hosting.md +130 -0
- package/dist/run-Bpg_ZRY8.js +1 -0
- package/dist/{run-DdYT3iHQ.js → run-BxYL-DaX.js} +333 -225
- package/dist/run-BxYL-DaX.js.map +1 -0
- package/dist/skill/SKILL.md +5 -3
- package/dist/skill/references/answers.md +36 -0
- package/dist/skill/references/mcp.md +9 -4
- package/dist/skill/references/sharing.md +55 -4
- package/dist/telemetry/flush-main.js +1 -1
- package/package.json +5 -5
- package/src/client.ts +1 -1
- package/src/commands/admin.ts +13 -3
- package/src/commands/authoring.ts +85 -3
- package/src/commands/index.ts +18 -3
- package/src/commands/remote.ts +209 -0
- package/src/commands/sharing.ts +33 -6
- package/src/commands/viewing.ts +20 -2
- package/src/detached.ts +3 -0
- package/src/docs.ts +12 -217
- package/src/exit.ts +2 -0
- package/src/mcp.ts +3 -21
- package/src/telemetry/store.ts +15 -4
- package/dist/bootstrap-Dc-SQHRF.js.map +0 -1
- package/dist/bootstrap-aaE5wFo9.js +0 -1
- package/dist/flush-C16w3JL8.js.map +0 -1
- package/dist/run-Bw4_6kcW.js +0 -1
- package/dist/run-DdYT3iHQ.js.map +0 -1
|
@@ -54,6 +54,15 @@
|
|
|
54
54
|
"explanation": "The action run's worker crashed, ran out of memory, was stopped by the event-loop watchdog, or the instance stopped while the run was running. The run ends `failed` with the reason `interrupted`, and Mostra never retries it by itself (D24): an action that had already started a side effect, such as sending an email, may or may not have finished it.",
|
|
55
55
|
"fix": "Look at the effect where it happens (the mail provider's sent folder, say) before running the action again. Pass the provider's own idempotency key from the action (for example, the run's key) so a repeated request can't act twice."
|
|
56
56
|
},
|
|
57
|
+
{
|
|
58
|
+
"code": "MOSTRA_ACTION_PAUSED",
|
|
59
|
+
"severity": "error",
|
|
60
|
+
"phase": "host",
|
|
61
|
+
"title": "Artifact paused, no actions run",
|
|
62
|
+
"hint": "Wait until the page is resumed, then run the action again.",
|
|
63
|
+
"explanation": "The artifact is paused, so its actions don't run: the run or call was refused before anything was recorded or sent to the owner's machine.",
|
|
64
|
+
"fix": "The owner resumes it with `mostra resume <artifact>`; a pause by the server's operator is resumed only by the operator."
|
|
65
|
+
},
|
|
57
66
|
{
|
|
58
67
|
"code": "MOSTRA_ACTION_RUN_NOT_FOUND",
|
|
59
68
|
"severity": "error",
|
|
@@ -99,6 +108,15 @@
|
|
|
99
108
|
"explanation": "Server function arguments and results cross a process boundary, so Mostra accepts exactly the types React documents for Server Functions (D54): strings, numbers, bigints, booleans, `undefined`, `null`, symbols registered with `Symbol.for`, arrays, `Map`, `Set`, typed arrays, `ArrayBuffer`, `Date`, `FormData`, plain objects, other server functions and promises. A result may also be an async iterable, whose items stream to the page. Mostra reports this code for anything else (a class instance, an `Error`, a `RegExp`, an object with a null prototype, a function that isn't a server function, an unregistered symbol, JSX) and names where in the value it is, such as `Argument 2 at .items[1]`. A promise in an argument that rejects fails the call the same way.",
|
|
100
109
|
"fix": "Convert the value to the supported types before the call or the return: `{ ...instance }` or a mapping for class instances, `error.message` for errors and `regexp.source` for regular expressions."
|
|
101
110
|
},
|
|
111
|
+
{
|
|
112
|
+
"code": "MOSTRA_ARTIFACT_BUNDLE_INVALID",
|
|
113
|
+
"severity": "error",
|
|
114
|
+
"phase": "host",
|
|
115
|
+
"title": "Not a bundle this version can import",
|
|
116
|
+
"hint": "Export the bundle again with `mostra export <artifact> --as bundle`, and import the files it wrote unchanged.",
|
|
117
|
+
"explanation": "Importing a bundle checks it before it keeps anything: its `mostra-bundle.json`, that its version ID is the one its artifact ID and digests give, and that its builds and source snapshot have the digests it records. This bundle failed one of those checks, so a file was changed, lost or added after it was exported, or it isn't a bundle Mostra wrote.",
|
|
118
|
+
"fix": "Export the version again from the home that published it, and copy the bundle's directory or archive whole."
|
|
119
|
+
},
|
|
102
120
|
{
|
|
103
121
|
"code": "MOSTRA_ARTIFACT_DIR_NOT_EMPTY",
|
|
104
122
|
"severity": "error",
|
|
@@ -612,6 +630,15 @@
|
|
|
612
630
|
"explanation": "A client sent `home.path` in `mostra/initialize`, and it names a different home from the one the instance locked at start-up. The home is chosen when the instance starts (`--home`, then `MOSTRA_HOME`, then the platform default), so `home.path` is a check: it stops a client from writing to a home it didn't mean.",
|
|
613
631
|
"fix": "Start the instance with `--home` set to the home the client expects, or connect to the socket of the instance that serves it. Leave `home.path` out to accept whichever home the instance serves."
|
|
614
632
|
},
|
|
633
|
+
{
|
|
634
|
+
"code": "MOSTRA_HOME_NETWORK_FILESYSTEM",
|
|
635
|
+
"severity": "error",
|
|
636
|
+
"phase": "host",
|
|
637
|
+
"title": "Data directory on a network filesystem",
|
|
638
|
+
"hint": "Put the server's data directory on a local disk.",
|
|
639
|
+
"explanation": "A remote server's data directory holds its hosted homes' ledgers and locks, which need a local disk: on a network filesystem a lock can seem held by two machines at once, and SQLite's WAL can't share memory across them (D165 item 0b). The server refuses a data directory it detects on NFS, SMB, AFP, WebDAV or a FUSE mount, before it opens anything.",
|
|
640
|
+
"fix": "Pass `--data` a directory on a local disk. To keep a copy elsewhere, replicate the homes with a backup tool instead."
|
|
641
|
+
},
|
|
615
642
|
{
|
|
616
643
|
"code": "MOSTRA_HOME_NOT_ALWAYS_ON",
|
|
617
644
|
"severity": "warning",
|
|
@@ -1071,6 +1098,141 @@
|
|
|
1071
1098
|
"explanation": "Verify rendered the newest version whose verdict passed and this source at the same viewport, clock and data, and the share of pixels the message gives differs between them. Any intended visual change shows here too.",
|
|
1072
1099
|
"fix": "If the change is one you made on purpose, nothing needs to change. To see where it is, read the ARIA snapshots, or look at the diff image the message names if you can view images."
|
|
1073
1100
|
},
|
|
1101
|
+
{
|
|
1102
|
+
"code": "MOSTRA_REMOTE_CONFIG_INVALID",
|
|
1103
|
+
"severity": "error",
|
|
1104
|
+
"phase": "host",
|
|
1105
|
+
"title": "Remote server configuration can't be used",
|
|
1106
|
+
"hint": "Fix the configuration key the message names, then start mostra-runtime server again.",
|
|
1107
|
+
"explanation": "`mostra-runtime server` reads its configuration (the file `--config` names and `MOSTRA_SERVER_*` variables) before it serves anything, and stops when a key is missing, of the wrong type or out of range, naming the key. Nothing was served.",
|
|
1108
|
+
"fix": "Correct the key the message names: `apiOrigin` must be an `https:` origin (or `http:` on loopback), and `domains.active` a host name."
|
|
1109
|
+
},
|
|
1110
|
+
{
|
|
1111
|
+
"code": "MOSTRA_REMOTE_HOME_MOVING",
|
|
1112
|
+
"severity": "error",
|
|
1113
|
+
"phase": "host",
|
|
1114
|
+
"title": "This account's pages are moving",
|
|
1115
|
+
"hint": "Try again in a minute: this account's pages are moving between machines.",
|
|
1116
|
+
"explanation": "The server's operator is moving this account's hosted home to another data directory (`drainHome`), so the home is closed here until it serves again. Clients retry; nothing is lost.",
|
|
1117
|
+
"fix": "Retry shortly; the move ends when the operator releases the home on its new machine."
|
|
1118
|
+
},
|
|
1119
|
+
{
|
|
1120
|
+
"code": "MOSTRA_REMOTE_HOME_SUSPENDED",
|
|
1121
|
+
"severity": "error",
|
|
1122
|
+
"phase": "host",
|
|
1123
|
+
"title": "This account's pages are suspended",
|
|
1124
|
+
"hint": "Contact the server's operator: this account's pages are suspended.",
|
|
1125
|
+
"explanation": "The server's operator suspended this account's hosted home: its pages, its owner instances' bindings, pushes and links are refused until the operator resumes it. Nothing was deleted.",
|
|
1126
|
+
"fix": "Ask the server's operator to resume the account."
|
|
1127
|
+
},
|
|
1128
|
+
{
|
|
1129
|
+
"code": "MOSTRA_REMOTE_LIMIT_REACHED",
|
|
1130
|
+
"severity": "error",
|
|
1131
|
+
"phase": "host",
|
|
1132
|
+
"title": "The server's limit refused this",
|
|
1133
|
+
"hint": "Read the message for the server's limit, and try again once it allows the operation.",
|
|
1134
|
+
"explanation": "The server's operator refused the operation for this account (its `limits` port): a share, a version push, a link, a view, a submission, an action or an MCP call. The message is the operator's own. A refused submission keeps its draft.",
|
|
1135
|
+
"fix": "Follow the operator's message; its `Retry-After`, when present, says when to try again."
|
|
1136
|
+
},
|
|
1137
|
+
{
|
|
1138
|
+
"code": "MOSTRA_REMOTE_LOGIN_FAILED",
|
|
1139
|
+
"severity": "error",
|
|
1140
|
+
"phase": "host",
|
|
1141
|
+
"title": "Signing in to a remote server failed",
|
|
1142
|
+
"hint": "Run mostra login again, and approve the code on the server's page within ten minutes.",
|
|
1143
|
+
"explanation": "Signing this home in to a remote server didn't finish: the code expired, the person refused it, the server refused the client, or the binding's access token was refused (revoked, expired, or for another server). Nothing of the home changed; artifacts it owns on that server stay its own.",
|
|
1144
|
+
"fix": "Sign in to the server again and approve the code on the page it names. A refusal you didn't expect means the sign-in was revoked on the server."
|
|
1145
|
+
},
|
|
1146
|
+
{
|
|
1147
|
+
"code": "MOSTRA_REMOTE_NO_INSTANCE",
|
|
1148
|
+
"severity": "error",
|
|
1149
|
+
"phase": "host",
|
|
1150
|
+
"title": "No owner instance connected",
|
|
1151
|
+
"hint": "Start Mostra on the machine linked to this account (mostra daemon start), then try again.",
|
|
1152
|
+
"explanation": "Creating, verifying and publishing from a chat host run on the account's default owner instance, through the relay (D165 item 5), and no default instance is connected to the server now. Reading tools (list, wait, results, state, docs, open) keep working.",
|
|
1153
|
+
"fix": "Start Mostra on the linked machine (`mostra daemon start`, or `mostra daemon install` to keep it running); link a machine first with `mostra login <server> --default`."
|
|
1154
|
+
},
|
|
1155
|
+
{
|
|
1156
|
+
"code": "MOSTRA_REMOTE_NOT_OWNER_INSTANCE",
|
|
1157
|
+
"severity": "error",
|
|
1158
|
+
"phase": "host",
|
|
1159
|
+
"title": "Another instance owns this hosted artifact",
|
|
1160
|
+
"hint": "Share or push this artifact from its owner instance, named in the message.",
|
|
1161
|
+
"explanation": "A hosted artifact has one owner instance: the one that shared it. It alone receives the artifact's submissions, relayed runs and authoring, and only it pushes versions of it (D165 item 1b). Another instance of the same account reads and waits through the hosted home.",
|
|
1162
|
+
"fix": "Run the command on the instance the message names. Moving an artifact to another owner instance isn't part of this release."
|
|
1163
|
+
},
|
|
1164
|
+
{
|
|
1165
|
+
"code": "MOSTRA_REMOTE_OPERATOR_UNAVAILABLE",
|
|
1166
|
+
"severity": "error",
|
|
1167
|
+
"phase": "host",
|
|
1168
|
+
"title": "The server's operator didn't answer",
|
|
1169
|
+
"hint": "Try again in a moment; the server's operator didn't answer in time.",
|
|
1170
|
+
"explanation": "The server's operator module didn't answer in time (2 s for limits, 5 s for sign-in), so an operation that creates something (a share, a push, a link, authoring, a sign-in) was refused rather than allowed blind. Views, drafts and submissions never wait for it, and existing sessions keep working.",
|
|
1171
|
+
"fix": "Try again; if it lasts, the server's operator has to fix its operator module."
|
|
1172
|
+
},
|
|
1173
|
+
{
|
|
1174
|
+
"code": "MOSTRA_REMOTE_OWNER_OFFLINE",
|
|
1175
|
+
"severity": "error",
|
|
1176
|
+
"phase": "host",
|
|
1177
|
+
"title": "The artifact's owner instance is offline",
|
|
1178
|
+
"hint": "Start Mostra on the machine that shared the page, or try again once it is back.",
|
|
1179
|
+
"explanation": "A hosted page called server code its owner instance runs, and the owner instance isn't connected. A plain call isn't kept, so it is refused at once; an action run waits or fails as the artifact's `hosted.offline` says.",
|
|
1180
|
+
"fix": "Start Mostra on the owner's machine (`mostra daemon start`, or `mostra daemon install` for always-on). An action that must work while the owner is away should be an action run with `hosted.offline.actions: \"queue\"`."
|
|
1181
|
+
},
|
|
1182
|
+
{
|
|
1183
|
+
"code": "MOSTRA_REMOTE_PAUSED_BY_OPERATOR",
|
|
1184
|
+
"severity": "error",
|
|
1185
|
+
"phase": "host",
|
|
1186
|
+
"title": "Paused by the server's operator",
|
|
1187
|
+
"hint": "Contact the server's operator: only the operator resumes a pause it made.",
|
|
1188
|
+
"explanation": "The server's operator paused this hosted artifact, and an owner can't undo an operator's pause (D165 item 14). Views keep working and the links stay valid.",
|
|
1189
|
+
"fix": "Ask the server's operator why it was paused and to resume it."
|
|
1190
|
+
},
|
|
1191
|
+
{
|
|
1192
|
+
"code": "MOSTRA_REMOTE_QUEUE_FULL",
|
|
1193
|
+
"severity": "error",
|
|
1194
|
+
"phase": "host",
|
|
1195
|
+
"title": "Too many runs wait for the owner",
|
|
1196
|
+
"hint": "Wait for the owner to come back and work through its queue, then press again.",
|
|
1197
|
+
"explanation": "The artifact's owner instance is offline and as many runs as the server allows already wait for it, so this one was refused before anything was recorded. Runs already waiting keep their place.",
|
|
1198
|
+
"fix": "Bring the owner instance back online: waiting runs then go out in the order they were made. The cap is the server's `relay.waitingRunsPerArtifact` setting."
|
|
1199
|
+
},
|
|
1200
|
+
{
|
|
1201
|
+
"code": "MOSTRA_REMOTE_RATE_LIMITED",
|
|
1202
|
+
"severity": "error",
|
|
1203
|
+
"phase": "host",
|
|
1204
|
+
"title": "Too many requests on this link",
|
|
1205
|
+
"hint": "Try again after the time the answer's Retry-After gives.",
|
|
1206
|
+
"explanation": "Too many requests of this kind came through one link or one address in a short time, past the server's `rateLimits`. Nothing was recorded, and a draft stays as it was.",
|
|
1207
|
+
"fix": "Wait for the `Retry-After` the answer carries and try again. The limits are the server's `rateLimits` settings."
|
|
1208
|
+
},
|
|
1209
|
+
{
|
|
1210
|
+
"code": "MOSTRA_REMOTE_SIGN_IN_REQUIRED",
|
|
1211
|
+
"severity": "error",
|
|
1212
|
+
"phase": "host",
|
|
1213
|
+
"title": "This action needs a signed-in viewer",
|
|
1214
|
+
"hint": "Sign in from the page's chrome, or have the owner allow this for anyone with the link.",
|
|
1215
|
+
"explanation": "On a hosted link, an action that runs on the owner's machine, or a submission when the artifact asks for it, needs a viewer signed in (D159, D165 item 13). Nothing was recorded.",
|
|
1216
|
+
"fix": "Sign in with the page's Sign in. An owner who wants anyone with the link to run actions sets `hosted: { actions: \"link\" }` in the manifest (and `submissions: \"link\"` for answers)."
|
|
1217
|
+
},
|
|
1218
|
+
{
|
|
1219
|
+
"code": "MOSTRA_REMOTE_UNDER_REVIEW",
|
|
1220
|
+
"severity": "error",
|
|
1221
|
+
"phase": "host",
|
|
1222
|
+
"title": "This page is under review",
|
|
1223
|
+
"hint": "Nothing to do here: the server's operator is reviewing this page.",
|
|
1224
|
+
"explanation": "The server's operator quarantined this hosted page, or this version of it, while it reviews it. Its data is kept; the page shows a neutral notice instead of its content until the operator releases it.",
|
|
1225
|
+
"fix": "The owner can ask the server's operator about the review."
|
|
1226
|
+
},
|
|
1227
|
+
{
|
|
1228
|
+
"code": "MOSTRA_REMOTE_UNREACHABLE",
|
|
1229
|
+
"severity": "error",
|
|
1230
|
+
"phase": "host",
|
|
1231
|
+
"title": "The remote server can't be reached",
|
|
1232
|
+
"hint": "Check the network and the server's address, then try again; mostra status shows the link.",
|
|
1233
|
+
"explanation": "The owner instance couldn't reach the remote server that holds this hosted artifact, so a write that must go there (its artifact state, a live value) was refused, never applied locally alone (D165 item 1). Nothing was lost: a page's edit stays in its journal and is sent again.",
|
|
1234
|
+
"fix": "Run `mostra status` to see each server's link. When the server is back the link reconnects by itself; then write again."
|
|
1235
|
+
},
|
|
1074
1236
|
{
|
|
1075
1237
|
"code": "MOSTRA_RUNTIME_BLANK",
|
|
1076
1238
|
"severity": "error",
|
|
@@ -1242,6 +1404,15 @@
|
|
|
1242
1404
|
"explanation": "The artifact has no submission yet, or none with the ID asked for. Submissions are durable once made, so this means none was made (or the ID belongs to another artifact or home). An artifact whose submission policy is `none` never has one, and the message says so: its viewers' work is in its shared state, its signals and its action runs.",
|
|
1243
1405
|
"fix": "Run `mostra wait <artifact> --until submitted` to block until the viewer submits, then read the results. List the artifact's submissions through `submission.created` events. Under policy `none`, read the shared state with `mostra state get <artifact>`, or wait for a signal the page raises with `mostra wait <artifact> --until signal:<name>`: its event carries the signal's payload."
|
|
1244
1406
|
},
|
|
1407
|
+
{
|
|
1408
|
+
"code": "MOSTRA_SUBMIT_PAUSED",
|
|
1409
|
+
"severity": "error",
|
|
1410
|
+
"phase": "host",
|
|
1411
|
+
"title": "Artifact paused, no answers taken",
|
|
1412
|
+
"hint": "Wait until the page is resumed, then submit again; the draft is kept.",
|
|
1413
|
+
"explanation": "The artifact is paused (`mostra pause`, or its server's operator paused it). A paused artifact stays viewable and its links stay valid, but it takes no submissions until it is resumed. Nothing was recorded, and the draft stays as it was.",
|
|
1414
|
+
"fix": "The owner resumes it with `mostra resume <artifact>`; a pause by the server's operator is resumed only by the operator."
|
|
1415
|
+
},
|
|
1245
1416
|
{
|
|
1246
1417
|
"code": "MOSTRA_SUBMIT_POLICY_NONE",
|
|
1247
1418
|
"severity": "error",
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_ACTION_PAUSED
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_ACTION_PAUSED
|
|
10
|
+
|
|
11
|
+
Artifact paused, no actions run. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The artifact is paused, so its actions don't run: the run or call was refused before anything was recorded or sent to the owner's machine.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
The owner resumes it with `mostra resume <artifact>`; a pause by the server's operator is resumed only by the operator.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Wait until the page is resumed, then run the action again.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_ARTIFACT_BUNDLE_INVALID
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_ARTIFACT_BUNDLE_INVALID
|
|
10
|
+
|
|
11
|
+
Not a bundle this version can import. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
Importing a bundle checks it before it keeps anything: its `mostra-bundle.json`, that its version ID is the one its artifact ID and digests give, and that its builds and source snapshot have the digests it records. This bundle failed one of those checks, so a file was changed, lost or added after it was exported, or it isn't a bundle Mostra wrote.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Export the version again from the home that published it, and copy the bundle's directory or archive whole.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Export the bundle again with `mostra export <artifact> --as bundle`, and import the files it wrote unchanged.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_HOME_NETWORK_FILESYSTEM
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_HOME_NETWORK_FILESYSTEM
|
|
10
|
+
|
|
11
|
+
Data directory on a network filesystem. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
A remote server's data directory holds its hosted homes' ledgers and locks, which need a local disk: on a network filesystem a lock can seem held by two machines at once, and SQLite's WAL can't share memory across them (D165 item 0b). The server refuses a data directory it detects on NFS, SMB, AFP, WebDAV or a FUSE mount, before it opens anything.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Pass `--data` a directory on a local disk. To keep a copy elsewhere, replicate the homes with a backup tool instead.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Put the server's data directory on a local disk.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_CONFIG_INVALID
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_CONFIG_INVALID
|
|
10
|
+
|
|
11
|
+
Remote server configuration can't be used. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
`mostra-runtime server` reads its configuration (the file `--config` names and `MOSTRA_SERVER_*` variables) before it serves anything, and stops when a key is missing, of the wrong type or out of range, naming the key. Nothing was served.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Correct the key the message names: `apiOrigin` must be an `https:` origin (or `http:` on loopback), and `domains.active` a host name.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Fix the configuration key the message names, then start mostra-runtime server again.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_HOME_MOVING
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_HOME_MOVING
|
|
10
|
+
|
|
11
|
+
This account's pages are moving. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The server's operator is moving this account's hosted home to another data directory (`drainHome`), so the home is closed here until it serves again. Clients retry; nothing is lost.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Retry shortly; the move ends when the operator releases the home on its new machine.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Try again in a minute: this account's pages are moving between machines.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_HOME_SUSPENDED
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_HOME_SUSPENDED
|
|
10
|
+
|
|
11
|
+
This account's pages are suspended. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The server's operator suspended this account's hosted home: its pages, its owner instances' bindings, pushes and links are refused until the operator resumes it. Nothing was deleted.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Ask the server's operator to resume the account.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Contact the server's operator: this account's pages are suspended.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_LIMIT_REACHED
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_LIMIT_REACHED
|
|
10
|
+
|
|
11
|
+
The server's limit refused this. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The server's operator refused the operation for this account (its `limits` port): a share, a version push, a link, a view, a submission, an action or an MCP call. The message is the operator's own. A refused submission keeps its draft.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Follow the operator's message; its `Retry-After`, when present, says when to try again.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Read the message for the server's limit, and try again once it allows the operation.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_LOGIN_FAILED
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_LOGIN_FAILED
|
|
10
|
+
|
|
11
|
+
Signing in to a remote server failed. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
Signing this home in to a remote server didn't finish: the code expired, the person refused it, the server refused the client, or the binding's access token was refused (revoked, expired, or for another server). Nothing of the home changed; artifacts it owns on that server stay its own.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Sign in to the server again and approve the code on the page it names. A refusal you didn't expect means the sign-in was revoked on the server.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Run mostra login again, and approve the code on the server's page within ten minutes.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_NOT_OWNER_INSTANCE
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_NOT_OWNER_INSTANCE
|
|
10
|
+
|
|
11
|
+
Another instance owns this hosted artifact. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
A hosted artifact has one owner instance: the one that shared it. It alone receives the artifact's submissions, relayed runs and authoring, and only it pushes versions of it (D165 item 1b). Another instance of the same account reads and waits through the hosted home.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Run the command on the instance the message names. Moving an artifact to another owner instance isn't part of this release.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Share or push this artifact from its owner instance, named in the message.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_NO_INSTANCE
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_NO_INSTANCE
|
|
10
|
+
|
|
11
|
+
No owner instance connected. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
Creating, verifying and publishing from a chat host run on the account's default owner instance, through the relay (D165 item 5), and no default instance is connected to the server now. Reading tools (list, wait, results, state, docs, open) keep working.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Start Mostra on the linked machine (`mostra daemon start`, or `mostra daemon install` to keep it running); link a machine first with `mostra login <server> --default`.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Start Mostra on the machine linked to this account (mostra daemon start), then try again.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_OPERATOR_UNAVAILABLE
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_OPERATOR_UNAVAILABLE
|
|
10
|
+
|
|
11
|
+
The server's operator didn't answer. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The server's operator module didn't answer in time (2 s for limits, 5 s for sign-in), so an operation that creates something (a share, a push, a link, authoring, a sign-in) was refused rather than allowed blind. Views, drafts and submissions never wait for it, and existing sessions keep working.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Try again; if it lasts, the server's operator has to fix its operator module.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Try again in a moment; the server's operator didn't answer in time.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_OWNER_OFFLINE
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_OWNER_OFFLINE
|
|
10
|
+
|
|
11
|
+
The artifact's owner instance is offline. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
A hosted page called server code its owner instance runs, and the owner instance isn't connected. A plain call isn't kept, so it is refused at once; an action run waits or fails as the artifact's `hosted.offline` says.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Start Mostra on the owner's machine (`mostra daemon start`, or `mostra daemon install` for always-on). An action that must work while the owner is away should be an action run with `hosted.offline.actions: "queue"`.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Start Mostra on the machine that shared the page, or try again once it is back.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_PAUSED_BY_OPERATOR
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_PAUSED_BY_OPERATOR
|
|
10
|
+
|
|
11
|
+
Paused by the server's operator. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The server's operator paused this hosted artifact, and an owner can't undo an operator's pause (D165 item 14). Views keep working and the links stay valid.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Ask the server's operator why it was paused and to resume it.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Contact the server's operator: only the operator resumes a pause it made.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_QUEUE_FULL
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_QUEUE_FULL
|
|
10
|
+
|
|
11
|
+
Too many runs wait for the owner. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The artifact's owner instance is offline and as many runs as the server allows already wait for it, so this one was refused before anything was recorded. Runs already waiting keep their place.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Bring the owner instance back online: waiting runs then go out in the order they were made. The cap is the server's `relay.waitingRunsPerArtifact` setting.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Wait for the owner to come back and work through its queue, then press again.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_RATE_LIMITED
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_RATE_LIMITED
|
|
10
|
+
|
|
11
|
+
Too many requests on this link. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
Too many requests of this kind came through one link or one address in a short time, past the server's `rateLimits`. Nothing was recorded, and a draft stays as it was.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Wait for the `Retry-After` the answer carries and try again. The limits are the server's `rateLimits` settings.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Try again after the time the answer's Retry-After gives.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_SIGN_IN_REQUIRED
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_SIGN_IN_REQUIRED
|
|
10
|
+
|
|
11
|
+
This action needs a signed-in viewer. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
On a hosted link, an action that runs on the owner's machine, or a submission when the artifact asks for it, needs a viewer signed in (D159, D165 item 13). Nothing was recorded.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Sign in with the page's Sign in. An owner who wants anyone with the link to run actions sets `hosted: { actions: "link" }` in the manifest (and `submissions: "link"` for answers).
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Sign in from the page's chrome, or have the owner allow this for anyone with the link.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_UNDER_REVIEW
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_UNDER_REVIEW
|
|
10
|
+
|
|
11
|
+
This page is under review. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The server's operator quarantined this hosted page, or this version of it, while it reviews it. Its data is kept; the page shows a neutral notice instead of its content until the operator releases it.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
The owner can ask the server's operator about the review.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Nothing to do here: the server's operator is reviewing this page.
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
---
|
|
2
|
+
code: MOSTRA_REMOTE_UNREACHABLE
|
|
3
|
+
severity: error
|
|
4
|
+
phase: host
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
<!-- Generated from packages/protocol/src/diagnostics/codes by `node tools/docs/diagnostics.ts write`. Edit the area file, not this page. -->
|
|
8
|
+
|
|
9
|
+
# MOSTRA_REMOTE_UNREACHABLE
|
|
10
|
+
|
|
11
|
+
The remote server can't be reached. Severity: error. Phase: host.
|
|
12
|
+
|
|
13
|
+
## What it means
|
|
14
|
+
|
|
15
|
+
The owner instance couldn't reach the remote server that holds this hosted artifact, so a write that must go there (its artifact state, a live value) was refused, never applied locally alone (D165 item 1). Nothing was lost: a page's edit stays in its journal and is sent again.
|
|
16
|
+
|
|
17
|
+
## How to fix it
|
|
18
|
+
|
|
19
|
+
Run `mostra status` to see each server's link. When the server is back the link reconnects by itself; then write again.
|
|
20
|
+
|
|
21
|
+
## Hint
|
|
22
|
+
|
|
23
|
+
Check the network and the server's address, then try again; mostra status shows the link.
|