Skip to content

Conversation

@hiyuchang
Copy link
Collaborator

@hiyuchang hiyuchang commented Jul 23, 2025

Description

As the title says.

Checklist

Please check the following items before code is ready to be reviewed.

  • Code has passed all tests
  • Docstrings have been added/updated in Google Style
  • Documentation has been updated
  • Code is ready for review

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Summary of Changes

Hello @hiyuchang, 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 significantly enhances the project's examples by introducing a dedicated Supervised Fine-Tuning (SFT) example. It provides all the necessary configuration files and documentation updates to guide users on how to perform SFT, specifically utilizing the Mixture-of-Thoughts dataset. The primary goal is to offer a robust and easily reproducible SFT use case.

Highlights

  • New SFT Example: I've added a complete example for Supervised Fine-Tuning (SFT) specifically tailored for the Mixture-of-Thoughts dataset. This provides a clear, runnable demonstration of SFT within the project.
  • Configuration Files: This PR introduces two new YAML configuration files: sft.yaml for the main SFT training parameters (including dataset specification and model settings) and train_sft.yaml for detailed trainer-specific configurations, such as FSDP settings and optimization parameters.
  • Documentation Updates: The existing documentation (example_dpo.md) has been updated to correctly reference the new SFT example's configuration file path and provide the correct command for running the SFT process.
  • Example Readme: A new README.md has been added within the examples/sft_mot directory to provide an overview of this specific SFT example, its purpose, and pointers to its configuration files and relevant documentation.
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 or fill out our survey to provide feedback.

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.

@hiyuchang
Copy link
Collaborator Author

/unittest-module-common

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a new example for Supervised Fine-Tuning (SFT), including configuration files and updated documentation. The changes are a valuable addition. My review focuses on improving the clarity, usability, and correctness of the new configuration files. I've suggested adding instructional comments for placeholder paths, aligning configuration parameters to prevent unexpected runtime behavior, and cleaning up the training config for better readability.

@hiyuchang
Copy link
Collaborator Author

/unittest-module-common

@github-actions
Copy link

Summary

Tests 📝 Passed ✅ Failed ❌ Skipped ⏭️ Other ❓ Flaky 🍂 Duration ⏱️
23 23 0 0 0 0 299ms

Tests

Test Name Status Flaky Duration
tests/common/config_test.py::TestConfig::test_all_examples_are_valid 2ms
tests/common/config_test.py::TestConfig::test_continue_from_checkpoint_is_valid 1ms
tests/common/config_test.py::TestConfig::test_load_default_config 4ms
tests/common/experience_test.py::TestEID::test_eid_properties 1ms
tests/common/experience_test.py::TestExperience::test_action_mask_and_logprobs_type 1ms
tests/common/experience_test.py::TestExperience::test_assertions 1ms
tests/common/experience_test.py::TestExperience::test_dpo_experience 1ms
tests/common/experience_test.py::TestExperience::test_gather 1ms
tests/common/experience_test.py::TestExperience::test_multi_turn_experience 1ms
tests/common/experience_test.py::TestExperience::test_serialize_deserialize 1ms
tests/common/experience_test.py::TestExperience::test_single_turn_experience 1ms
tests/common/experience_test.py::TestExperience::test_to_dict 1ms
tests/common/experience_test.py::TestExperienceConversion::test_batch_conversion 1ms
tests/common/experience_test.py::TestExperienceConversion::test_dpo_experience_batch_conversion 1ms
tests/common/experience_test.py::TestExperienceConversion::test_experience_model_experience_conversion 1ms
tests/common/experience_test.py::TestExperienceConversion::test_multiturn_experience_batch_converstion 1ms
tests/common/vllm_test.py::ModelWrapperTest_0::test_generate 46ms
tests/common/vllm_test.py::ModelWrapperTest_1::test_generate 54ms
tests/common/vllm_test.py::ModelWrapperTest_2::test_generate 56ms
tests/common/vllm_test.py::ModelWrapperTest_3::test_generate 42ms
tests/common/vllm_test.py::ModelWrapperTest_4::test_generate 54ms
tests/common/vllm_test.py::TestAPIServer::test_api 33ms
tests/common/vllm_test.py::TestTokenizer::test_assistant_token_mask 1ms

Github Test Reporter by CTRF 💚

@pan-x-c pan-x-c merged commit aca040f into modelscope:main Jul 23, 2025
2 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.

2 participants