-
Notifications
You must be signed in to change notification settings - Fork 905
Fix: Use DDP for PPO traning will cause AttributeError: 'DistributedDataParallel' object has no attribute 'config' error #5822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this 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 @kiritoxkiriko, 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 a critical bug in the PPO trainer when utilizing Distributed Data Parallel (DDP) for training. It resolves an AttributeError
that previously occurred during model saving, which was caused by the trl
library's internal create_model_card
function attempting to access configuration directly from a DDP-wrapped model. The implemented solution ensures that the model is correctly unwrapped before saving, thereby preventing crashes and enabling seamless checkpointing during distributed PPO training.
Highlights
- Bug Fix for DDP PPO Training: This pull request resolves an
AttributeError
that occurs when saving a model during PPO training with Distributed Data Parallel (DDP) enabled, specifically whentrl
version is 0.20.0 or higher. - Root Cause Identification: The error stems from
trl
'screate_model_card
function attempting to accessself.model.config
directly on aDistributedDataParallel
object, which does not expose theconfig
attribute directly. - Model Unwrapping Mechanism: The fix involves temporarily unwrapping the DDP model before calling the superclass's
_save_checkpoint
method, allowingtrl
to access the underlying model's configuration, and then restoring the DDP-wrapped model afterwards.
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.
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 correctly fixes an AttributeError
during PPO training with DDP by unwrapping the model before saving a checkpoint. The overall change is good. I've provided one suggestion to improve the robustness of the implementation by using a try...finally
block. This ensures the model's state is correctly restored even if an error occurs during the checkpointing process.
thanks for your contribution please pass the lint test |
use more robust error check Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
095442c
to
e70b3a5
Compare
e70b3a5
to
6aa4c30
Compare
passed |
PR type
PR information
When trl >= 0.20.0
When use DDP for ppo, save model will return AttributeError: 'DistributedDataParallel' object has no attribute 'config'.
This pr fix the error occured when save model after training #5287, but this issue will trigger when save ckpt during traning.
Before call
_save_checkpoint
, trl will callcreate_model_card
to create model card, which will use valuemodel.config
, which will not exist in ddp model, so we need to unwrap it, see:This PR will fix this by unwraping the DDP model before call
_save_checkpoint
.Experiment results
Paste your experiment result here(if needed).