fix(api): resolve TypeError in chat/completions route

[diegosouzapw]

Bug: Cannot read properties of undefined (reading 'then') in every chat completion request.

Root cause: initTranslators() in open-sse/translator/index.js is a no-op stub returning undefined (translators self-register via static imports). The route called .then() on it.

Fix: Wrapped with Promise.resolve() so .then() works regardless of return type.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[github-actions]

@codex review

[gemini-code-assist]

Summary of Changes

Hello @diegosouzapw, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical TypeError that prevented chat completion requests from functioning correctly. The issue stemmed from an asynchronous initialization function returning an undefined value, which subsequently caused a runtime error when attempting to chain a .then() call. The fix ensures robust handling of the initialization process by explicitly converting the return value into a resolved Promise, thereby stabilizing the chat completion API.

Highlights

• Bug Fix: Resolved a TypeError: Cannot read properties of undefined (reading 'then') that occurred in every chat completion request.
• Root Cause Identified: The initTranslators() function in open-sse/translator/index.js was a no-op stub returning undefined, and the chat completion route attempted to call .then() on this undefined value.
• Solution Implemented: Wrapped the call to initTranslators() with Promise.resolve() to ensure that the result is always a Promise-like object, allowing .then() to be called safely regardless of the original return type.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• src/app/api/v1/chat/completions/route.js
  • Wrapped initTranslators() with Promise.resolve() to prevent TypeError.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[chatgpt-codex-connector]

To use Codex here, create a Codex account and connect to github.

[gemini-code-assist]

Code Review

This pull request correctly resolves a TypeError that occurred when initializing translators. The fix wraps the call to initTranslators() in Promise.resolve() to ensure a promise is always returned. My review includes a suggestion to use an async IIFE, which would make the initialization logic even more robust by caching any potential initialization failures, improving the overall reliability of the singleton initialization pattern.

[gemini-code-assist]

While Promise.resolve() correctly fixes the TypeError, using an async IIFE (Immediately Invoked Function Expression) would make the logic slightly more robust, especially regarding error handling. If initTranslators() were to throw an error, this approach would cache the resulting rejected promise, preventing repeated failing attempts on subsequent calls. This improves predictability and aligns well with the singleton pattern you're using for initialization.

    initPromise = (async () => {
      await initTranslators();
      console.log("[SSE] Translators initialized");
    })();

[Copilot]

Pull request overview

This PR fixes a TypeError that occurred in every chat completion request to /v1/chat/completions. The bug was caused by calling .then() on the return value of initTranslators(), which is a no-op stub function returning undefined (translators self-register via static imports at module load time). The fix wraps the call with Promise.resolve() to ensure it always returns a Promise that can be chained with .then().

Changes:

• Wrapped initTranslators() call with Promise.resolve() in the ensureInitialized function to handle the undefined return value

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.