fix(client): tolerate script replay after command completion
This commit is contained in:
1 parent
6984a09486
commit
1b5c6dbf98
5 files changed
+180
-2
No files matched your search
@@ -20,6 +20,7 @@ initial evidence; do not restart services or resubmit work merely to inspect it.
|
||||
| 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 `terminal command cannot accept script data` | Upload replay can race the finished command's pending event replay. Corrected clients ignore stale script frames for confirmed local terminal commands and let events drain, without modifying script bytes or relaunching. Upgrade the client and retain spool/history. A terminal-script error for a still-live command remains a protocol failure. |
|
||||
| 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. |
|
||||
|
||||
Reference in new issue
Block a user