-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[Model Averaging] Code simplification for _find_process_group function #75007
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
🔗 Helpful links
💊 CI failures summary and remediationsAs of commit 03447c3 (more details on the Dr. CI page):
🕵️ 1 new failure recognized by patternsThe following CI failures do not appear to be due to upstream breakages
|
rohan-varma
left a comment
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.
Lgtm, thanks!
|
@rohan-varma has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
|
CI error is unrelated - |
#75007) Summary: Previously the highest-level process group in `period_process_group_dict` could be `None`, indicating the global group. Now `period_process_group_dict` cannot contain `None` as a process group, so the function `_find_process_group` can just return a process group instead of a tuple -- when not found, just return `None`, because now the returned process group cannot be `None`. Proposal: #71325 Pull Request resolved: #75007 Reviewed By: awgu Differential Revision: D35357816 Pulled By: rohan-varma fbshipit-source-id: 4522dba49797df7140227bfd822d668b7e118a66
|
Hey @wayi1. |
Previously the highest-level process group in
period_process_group_dictcould beNone, indicating the global group. Nowperiod_process_group_dictcannot containNoneas a process group, so the function_find_process_groupcan just return a process group instead of a tuple -- when not found, just returnNone, because now the returned process group cannot beNone.Proposal: #71325