From f4dc96f1b0db53e80708775f65494eb3973a89d0 Mon Sep 17 00:00:00 2001 From: Eric Seastrand Date: Fri, 6 Mar 2026 19:48:13 -0600 Subject: [PATCH] fix(happy-app): include server error details in RPC failure messages Instead of the opaque "RPC call failed", surface the actual error reason from the server (e.g. "RPC method not available", timeout, etc.). Generated with [Claude Code](https://claude.ai/code) via [Happy](https://happy.engineering) Co-Authored-By: Claude Co-Authored-By: Happy --- packages/happy-app/sources/sync/apiSocket.ts | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/happy-app/sources/sync/apiSocket.ts b/packages/happy-app/sources/sync/apiSocket.ts index 7e64ae5835..6cfa718ecb 100644 --- a/packages/happy-app/sources/sync/apiSocket.ts +++ b/packages/happy-app/sources/sync/apiSocket.ts @@ -125,7 +125,7 @@ class ApiSocket { if (result.ok) { return await sessionEncryption.decryptRaw(result.result) as R; } - throw new Error('RPC call failed'); + throw new Error(`RPC call failed: ${result.error || 'unknown error'}`); } /** @@ -145,7 +145,7 @@ class ApiSocket { if (result.ok) { return await machineEncryption.decryptRaw(result.result) as R; } - throw new Error('RPC call failed'); + throw new Error(`RPC call failed: ${result.error || 'unknown error'}`); } send(event: string, data: any) {