Keep SQL Experience Buffer behavior consistent with previous versions#248
Conversation
There was a problem hiding this comment.
Summary of Changes
Hello @pan-x-c, I'm Gemini Code Assist1! 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 refines the data handling and state management within the system to improve the robustness and flexibility of training processes. Key changes include updating the SQL experience buffer's read logic to maintain consistent behavior for certain data types and enabling seamless continuous training for SFT and DPO models. Additionally, the core state management component has been renamed for clarity and its functionality extended to better support persistent training states.
Highlights
- SQL Experience Buffer Behavior: The SQL Experience Buffer now sorts experiences based on their consumption count, prioritizing less consumed experiences. This ensures consistency with previous versions' behavior for 'experience' schema types, while SFT and DPO schema types will use a FIFO (First-In, First-Out) approach.
- State Management Renaming: The
CacheManagerclass and its associated file have been renamed toStateManagerto more accurately reflect its role in managing the running state of the Explorer and Trainer components. - Continuous Training Support: Enhanced support for continuing training for SFT (Supervised Fine-Tuning) and DPO (Direct Preference Optimization) models has been implemented. The
StateManagernow tracks and persists the latest task and experience indices, allowing training to resume from a specific point.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request introduces several enhancements, including making the SQL Experience Buffer behavior consistent with previous versions by sorting experiences based on consumption count, renaming CacheManager to StateManager for clarity, and adding support for continuing SFT and DPO training. The changes are well-structured. I've found a potential bug in how the trainer state is saved, which could affect resuming training, and a minor code duplication issue in the tests. My detailed feedback is in the comments below.
|
/unittest-all |
|
/unittest-all |
|
/unittest-all |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-trainer |
Summary
Failed Tests
Skipped
Tests
Github Test Reporter by CTRF 💚 |
|
/unittest-module-trainer |
Summary
Skipped
Tests
Github Test Reporter by CTRF 💚 |
Description
Checklist
Please check the following items before code is ready to be reviewed.