fix(sync): disable cloud sync and truncate error logs

[diegosouzapw]

CLOUD_URL was pointing to omniroute.com which doesn't have a /sync/ endpoint, causing repeated 404 HTML dumps in console logs.

[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.

[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 an issue where the application was repeatedly attempting to sync with a non-existent cloud endpoint, leading to excessive 404 error logs. The changes disable the problematic cloud synchronization feature by default and improve the error logging mechanism to prevent console spam from large error responses.

Highlights

• Cloud Sync Disablement: The CLOUD_URL and NEXT_PUBLIC_CLOUD_URL environment variables in .env.example have been cleared, effectively disabling cloud synchronization to prevent calls to a non-existent endpoint.
• Error Log Truncation: Cloud sync error logging in src/lib/cloudSync.js has been enhanced to truncate lengthy error messages to 200 characters and include the HTTP status code, preventing console spam from large HTML responses.

🧠 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

• .env.example
  • Cleared the CLOUD_URL and NEXT_PUBLIC_CLOUD_URL variables to disable cloud sync by default.
• src/lib/cloudSync.js
  • Modified the error logging for cloud sync failures to truncate long error messages.
  • Included the HTTP status code in the cloud sync failure log message.

Activity

• The pull request was created by diegosouzapw.
• No review comments or further activity have been recorded yet.

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. ↩

[github-actions]

@codex review

[chatgpt-codex-connector]

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

[gemini-code-assist]

Code Review

This pull request addresses an issue with cloud sync where a misconfigured URL was causing errors and large log outputs. The changes disable cloud sync by default in the example environment file and truncate long error messages from sync failures to improve log readability. My review includes a suggestion to replace a magic number with a constant for better code maintainability.

[gemini-code-assist]

Using a magic number like 200 for the truncation length can make the code harder to understand and maintain. It's better to extract it into a named constant to clarify its purpose.

Suggested change

	const truncated = errorText.length > 200 ? errorText.slice(0, 200) + "…" : errorText;
	const MAX_ERROR_LOG_LENGTH = 200;
	const truncated = errorText.length > MAX_ERROR_LOG_LENGTH ? errorText.slice(0, MAX_ERROR_LOG_LENGTH) + "…" : errorText;

[Copilot]

Pull request overview

This PR disables the cloud sync feature by clearing the CLOUD_URL configuration and improves error logging to prevent 404 HTML responses from flooding console logs. The changes address an issue where CLOUD_URL was pointing to omniroute.com which doesn't have a /sync/ endpoint, causing repeated verbose HTML error dumps in the logs.

Changes:

• Set CLOUD_URL and NEXT_PUBLIC_CLOUD_URL to empty strings in .env.example to disable cloud sync by default
• Add error response truncation (200 chars) and include HTTP status codes in cloud sync failure logs

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.env.example	Clears CLOUD_URL and NEXT_PUBLIC_CLOUD_URL values to disable cloud sync
src/lib/cloudSync.js	Truncates error responses to 200 characters and includes HTTP status in log messages

---

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

[Copilot]

The truncation logic added here is excellent for preventing large HTML error responses from flooding the logs. However, there's a similar error logging pattern in src/app/api/sync/cloud/route.js at line 124-125 (console.log("Cloud disable failed:", errorText)) that could benefit from the same truncation logic for consistency. Consider applying the same pattern there to prevent similar issues when cloud disable operations fail.

[Absorber97]

Implemented in 4d6efe69b. Private combo catalog/API-key isolation now validates isHidden, gates combo discovery and invocation through allowedCombos independently of leaf allowedModels, covers bare auto routing, and reconciles live active model metadata with exact connection scope. Focused catalog/policy tests pass; typechecks, lint, cycles, Vitest 368/368, and production build pass.