Skip to content

fix megatron weights sync#128

Merged
tastelikefeet merged 1 commit intomodelscope:mainfrom
hjh0119:fix-mg-sync
Mar 26, 2026
Merged

fix megatron weights sync#128
tastelikefeet merged 1 commit intomodelscope:mainfrom
hjh0119:fix-mg-sync

Conversation

@hjh0119
Copy link
Copy Markdown
Collaborator

@hjh0119 hjh0119 commented Mar 26, 2026

No description provided.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, 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 addresses an issue with the Megatron model's weight synchronization process. The core change involves a significant refactoring of the underlying asynchronous communication logic, aiming to enhance reliability and simplify the handling of potential errors during weight transfer.

Highlights

  • Weight Synchronization Refactor: The mechanism for synchronizing Megatron model weights has been refactored. The previous queue.Queue-based approach for sending weights asynchronously in a separate thread has been replaced with a more direct asyncio call within a dedicated thread, streamlining the process and improving error propagation.

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

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.

Copy link
Copy Markdown
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 refactors the weight_generator function in src/twinkle/model/megatron/megatron.py to simplify the asynchronous weight sending mechanism. The previous queue-based producer-consumer pattern is replaced with a more direct approach where engine.send_weights is called asynchronously within a dedicated thread, with error handling managed via a result_container. A review comment suggests simplifying the manual asyncio event loop management by utilizing asyncio.run() for improved conciseness and robustness.

@tastelikefeet tastelikefeet merged commit 4d6ebeb into modelscope:main Mar 26, 2026
1 of 3 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