v6.6.56

[luispater]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @luispater, 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 primarily enhances the system's ability to manage and track usage data by introducing export and import capabilities for request statistics. It also refines the authentication indexing mechanism to provide a more stable and consistent identifier for authentication records. Additionally, the project's documentation has been updated to include a new integration.

Highlights

• Usage Data Management: Introduced new API endpoints for exporting and importing usage statistics, allowing for backup and migration of historical request data. The import functionality includes logic to merge snapshots and deduplicate entries.
• Stable Authentication Indexing: Refactored the authentication index (AuthIndex) from a monotonically increasing uint64 to a stable string derived from a hash of authentication metadata (filename, API key, or ID). This change improves consistency and reliability of auth indexing across restarts.
• Documentation Update: Added 'Quotio' to the list of projects based on CLIProxyAPI in both the English and Chinese README files.
• Type Refactoring: Updated the AuthIndex field across multiple internal and SDK components (e.g., usageReporter, RequestDetail, Record) to reflect the change from uint64 to string.

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

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

[gemini-code-assist]

Code Review

This pull request introduces a valuable feature for exporting and importing usage statistics, which is great for backup and migration purposes. The implementation of the new API endpoints and the logic for merging statistics snapshots seems solid. Additionally, the refactoring of AuthIndex from a numeric ID to a stable, hash-based string is a significant improvement for consistency and reliability across restarts. I've found one area with minor code duplication that could be refactored for better maintainability. Overall, these are great changes.

[gemini-code-assist]

The logic in this new normaliseTokenStats function is identical to the logic within the existing normaliseDetail function (lines 447-452). This introduces code duplication. To improve maintainability, you could refactor normaliseDetail to use this new normaliseTokenStats function, which would centralize the token normalization logic.