Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneesstack72

Relationships

#1993 LockTimeoutError surfaces as generic 'internal error' at the CLI

Opened by stack72 · 9/3/2026· Shipped 9/3/2026

When a per-instance lock times out in swamp serve, the CLI sees 'Server reported method_execution_failed: An internal error occurred'. Nothing tells the client that the failure is a transient lock timeout worth retrying. The S3 and GCS datastore extensions now throw LockTimeoutError with code='LOCK_TIMEOUT' and retryable=true (lab #1980 fix). The serve handler in model_handlers.ts should map LockTimeoutError to a specific method-execution outcome the CLI can act on, rather than the generic 'internal error'.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 7 MOREPR_MERGED+ 2 MORESESSION_SUMMARIZED

Shipped

9/3/2026, 11:04:40 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
stack72 assigned stack729/3/2026, 10:07:16 PM

Sign in to post a ripple.