Skip to content

Conversation

@rsproule
Copy link
Contributor

No description provided.

@railway-app
Copy link

railway-app bot commented Oct 17, 2025

🚅 Deployed to the echo-pr-582 environment in echo

Service Status Web Updated (UTC)
echo ◻️ Removed (View Logs) Web Oct 17, 2025 at 7:25 pm

@vercel
Copy link
Contributor

vercel bot commented Oct 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
assistant-ui-template Ready Ready Preview Comment Oct 17, 2025 7:20pm
echo-control Ready Ready Preview Comment Oct 17, 2025 7:20pm
echo-next-boilerplate Ready Ready Preview Comment Oct 17, 2025 7:20pm
echo-next-image Ready Ready Preview Comment Oct 17, 2025 7:20pm
echo-next-sdk-example Ready Ready Preview Comment Oct 17, 2025 7:20pm
echo-video-template Ready Ready Preview Comment Oct 17, 2025 7:20pm
echo-vite-sdk-example Ready Ready Preview Comment Oct 17, 2025 7:20pm
next-chat-template Ready Ready Preview Comment Oct 17, 2025 7:20pm
react-boilerplate Ready Ready Preview Comment Oct 17, 2025 7:20pm
react-chat Ready Ready Preview Comment Oct 17, 2025 7:20pm
react-image Ready Ready Preview Comment Oct 17, 2025 7:20pm
1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
component-registry Skipped Skipped Oct 17, 2025 7:20pm

expect(streamed).not.toBe('');
} catch (err) {
const details = getApiErrorDetails(err);
throw new Error(`[generateText] Groq ${model_id} failed: ${details}`);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The error message in the streamText test incorrectly identifies itself as a generateText test, which could cause confusion when debugging test failures.

View Details
📝 Patch Details
diff --git a/packages/tests/provider-smoke/gemini-stream-text.test.ts b/packages/tests/provider-smoke/gemini-stream-text.test.ts
index 086995ce..0fa669d5 100644
--- a/packages/tests/provider-smoke/gemini-stream-text.test.ts
+++ b/packages/tests/provider-smoke/gemini-stream-text.test.ts
@@ -38,7 +38,7 @@ describe.concurrent('Gemini streamText per model', () => {
         expect(streamed).not.toBe('');
       } catch (err) {
         const details = getApiErrorDetails(err);
-        throw new Error(`[generateText] Gemini ${model_id} failed: ${details}`);
+        throw new Error(`[streamText] Gemini ${model_id} failed: ${details}`);
       }
     });
   }
diff --git a/packages/tests/provider-smoke/groq-stream-text.test.ts b/packages/tests/provider-smoke/groq-stream-text.test.ts
index 05e663c1..d3a86d2d 100644
--- a/packages/tests/provider-smoke/groq-stream-text.test.ts
+++ b/packages/tests/provider-smoke/groq-stream-text.test.ts
@@ -35,7 +35,7 @@ describe.concurrent('Groq streamText per model', () => {
         expect(streamed).not.toBe('');
       } catch (err) {
         const details = getApiErrorDetails(err);
-        throw new Error(`[generateText] Groq ${model_id} failed: ${details}`);
+        throw new Error(`[streamText] Groq ${model_id} failed: ${details}`);
       }
     });
   }

Analysis

Incorrect error message labels in streamText tests

What fails: groq-stream-text.test.ts and gemini-stream-text.test.ts use [generateText] in error messages instead of [streamText], causing confusion when debugging test failures

How to reproduce:

  • Run a streamText test that fails (e.g., invalid API key)
  • Error message incorrectly shows [generateText] Groq model failed instead of [streamText] Groq model failed

Result: Misleading error messages that misidentify the failing operation as generateText when it's actually streamText

Expected: Error messages should use [streamText] to match the actual test purpose, consistent with anthropic-stream-text.test.ts, openai-stream-text.test.ts, and openrouter-stream-text.test.ts

@rsproule rsproule merged commit 9584440 into master Oct 17, 2025
19 of 21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants