Skip to content

[examples] flux-control: use num_training_steps_for_scheduler #11662

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

Merged
merged 2 commits into from
Jun 5, 2025

Conversation

Markus-Pobitzer
Copy link
Contributor

[examples] flux-control: use num_training_steps_for_scheduler in get_scheduler instead of args.max_train_steps * accelerator.num_processes

What does this PR do?

Fixes #11661
Closes #11661

By using the already prepared num_training_steps_for_scheduler in the intended way, we make sure that the args.max_train_steps variable gets not accessed in case it is None.

Before submitting

Who can review?

@sayakpaul

Markus-Pobitzer and others added 2 commits June 5, 2025 10:00
@HuggingFaceDocBuilderDev

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@sayakpaul sayakpaul merged commit 745199a into huggingface:main Jun 5, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants