Skip to content

Integrate dumper in miles#766

Open
fzyzcjy wants to merge 1 commit intomainfrom
ac8452/1/0
Open

Integrate dumper in miles#766
fzyzcjy wants to merge 1 commit intomainfrom
ac8452/1/0

Conversation

@fzyzcjy
Copy link
Collaborator

@fzyzcjy fzyzcjy commented Mar 20, 2026

No description provided.

Add dumper CLI arguments (--dumper-enable, --dumper-dir, per-phase config),
dumper_utils.py for SGLang/Megatron dumper integration, model.py hooks
for forward-only and forward-backward phases, rollout env var plumbing,
source patcher wiring in training actors, and basic e2e test.
@gemini-code-assist
Copy link
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 significantly enhances the debugging and analysis capabilities within the Miles framework by integrating a powerful data dumper. The primary goal is to provide developers with detailed insights into the internal states of models and data flows during both inference and training phases. This integration allows for granular control over what data is dumped and when, facilitating easier identification and resolution of issues, and supporting in-depth post-hoc analysis without altering the core logic of the system.

Highlights

  • Dumper Utility Integration: Added core dumper utility functions and integration hooks to enable data dumping across different phases of the Miles framework, including SGLang inference and Megatron training (forward-only and forward-backward).
  • Configuration and Control: Introduced new command-line arguments to control dumper behavior, such as enabling it, specifying output directories, and configuring phase-specific settings and source patchers.
  • Comprehensive Testing: Included both end-to-end (E2E) tests to validate the dumper's functionality in a full training pipeline and unit tests for the newly added dumper utility functions, ensuring robustness and correctness.
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
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 dumper utility into the miles framework, supporting FSDP and Megatron training backends, as well as SGLang inference. The changes include new command-line arguments, a dumper_utils.py file, and comprehensive tests. The implementation handles distributed environments and provides flexible configuration. A limitation regarding virtual pipeline parallelism in the _extract_model method is noted, with a suggestion to add a TODO for future improvement.

Comment on lines +88 to +92
def _extract_model(model: Sequence[torch.nn.Module]) -> torch.nn.Module:
assert (
len(model) == 1
), f"Dumper does not yet support virtual pipeline parallelism (got {len(model)} model chunks)"
return model[0]
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The _extract_model method explicitly states that the dumper does not yet support virtual pipeline parallelism. Consider adding a TODO to address this limitation in future iterations, especially if virtual pipeline parallelism is a planned feature, to ensure full compatibility.

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.

1 participant