-
Notifications
You must be signed in to change notification settings - Fork 22.6k
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
[FSDP] Fix bug in determining whether parameters need to be materialized #97488
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/97488
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 723f8b9: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
Test? |
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.
Great catch! Thanks!
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Previously,
_need_to_materialize_module
would return false because:managed_params =_get_orig_params(module, ignored_params)
returns a generatoris_meta_module = any(param.is_meta for param in managed_params)
exhausts the generator in its checkany(fake.is_fake(param) for param in managed_params)
would try to iterate over the empty generator and get an empty sequence, thus returningFalse