From 9dcb45d1ab7cfa0525a304c470bc5bc9b160f373 Mon Sep 17 00:00:00 2001
From: Ann Zhang <ann.zhang@databricks.com>
Date: Mon, 18 May 2026 17:10:53 -0700
Subject: [PATCH] Fix: convert mid-stream errors to data-error parts for OAuth
 chip rendering
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Raw error chunks ({ type: 'error', errorText }) were forwarded as-is to the
client, which only renders data-error parts. This meant OAuth credential errors
never surfaced as the login chip — they were logged but silently dropped by
the client's message rendering pipeline.

Co-authored-by: Ann Zhang
---
 e2e-chatbot-app-next/server/src/lib/stream-fallback.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/e2e-chatbot-app-next/server/src/lib/stream-fallback.ts b/e2e-chatbot-app-next/server/src/lib/stream-fallback.ts
index ed722bf7..41e13d7c 100644
--- a/e2e-chatbot-app-next/server/src/lib/stream-fallback.ts
+++ b/e2e-chatbot-app-next/server/src/lib/stream-fallback.ts
@@ -34,7 +34,7 @@ export async function drainStreamToWriter(
           'Mid-stream error, forwarding to client:',
           chunk.value.errorText,
         );
-        writer.write(chunk.value);
+        writer.write({ type: 'data-error', data: chunk.value.errorText ?? chunk.value.message ?? 'Unknown error' });
       } else {
         if (!receivedTextChunk && chunk.value.type.startsWith('text-')) {
           receivedTextChunk = true;