fix(transport): align WebSocket read limits with agent protocol

This commit is contained in:
cabbage committed 2026-11-09 07:53:18 +00:00
1 parent ef6e65e6f1
commit 6984a09486
11 files changed
+376 -4

No files matched your search

+1 -1
View File
@@ -8,7 +8,7 @@ description: "Operate and troubleshoot RVBox deployments through rvc and the Con
Use the deployment already present. Discover its addresses, paths, accounts,
versions, and supported capabilities; never substitute a remembered test host,
container name, credential, client ID, or filesystem layout. This reference
matches RVBox v1 source reviewed on 2026-10-27: Linux server and Windows client.
matches RVBox v1 source reviewed on 2026-11-09: Linux server and Windows client.
Unix-like client implementation is outside that release.
## Establish the control route
@@ -19,6 +19,7 @@ initial evidence; do not restart services or resubmit work merely to inspect it.
| Socket permission denied | Run as the existing socket owner through the deployment route; inspect directory traversal and mount permissions. Do not chmod the control socket world-accessible. |
| Client missing or NOT_FOUND | List all client pages; verify the exact registered ID and server instance. A hostname assumption or wrong Compose project can select different state. Retention can also remove command history. |
| Disconnected / OFFLINE / UNAVAILABLE | Separate server recovery from client connectivity. Inspect SCM, WSS hostname/path, proxy WebSocket upgrade, certificate/time/CA, DNS, reconnect logs, and pending instance conflicts. Missing optional HTTP health is not proof of a stopped daemon. |
| `StatusMessageTooBig` / `read limited at 32769 bytes` after output or during reconnect | Early v1 WebSocket readers kept the library's 32 KiB default despite allowing larger protocol envelopes. Upgrade the server first to accept pending output, then the client for large incoming dispatch/history. Preserve spool/history; rebooting replays the same pending message. Corrected readers use the configured envelope ceiling, normally 1 MiB. |
| Repeated `signal command ...: command is not running` | An older client disconnects on a late signal instead of persisting its rejection. Upgrade the client while retaining config/spool/history; corrected builds acknowledge the signal without disconnecting. Do not wipe state or reissue the original command. |
| QUEUED persists | Check connection, supported shell, queue/running capacity, acceptance events, and queue expiry. Queuing does not promise execution, and queue TTL is not a runtime timeout. |
| CLI deadline / broken stream | Work may still run. Query the captured issue and resume history via the API. For uncertain admission, retry only with the same request ID and payload. |
@@ -38,6 +39,16 @@ immediate repeated calls will succeed. Do not parse error text into invented
stable exit-code classes: the current CLI normally exits 1 for its own errors
and exposes remote lifecycle separately.
On Windows, SCM startup and reconnect diagnostics are written to
`%ProgramData%\RVBox\service-startup.log`, independently of optional
observability logging. Inspect recent entries around the failure before
restarting. The tray's log action may select the configured runtime log instead;
an empty/missing runtime log does not mean the service recorded no diagnostics.
Corrected servers log bounded WebSocket read/reconciliation errors without
command payloads, and count `agent_message_too_big` failures. Earlier clients
reported the placeholder daemon version `v1`; use the installed executable's
`--version` or PE product version when the server cannot identify the release.
## Windows identity, GUI, and shells
`--elevated` is the only execution-context request toggle. Selection and