-
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
[c10d] delete lengths offset checks #98368
Conversation
According to @kewen2501, NCCL supports up to size_t send counts, so PGNCCL shouldn't restrict it A follow up is to think about whether we should add overflow protection of offset [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/98368
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 1 FailuresAs of commit 9e217c6: BROKEN TRUNK - The following jobs failed but were present on the merge base a6bd21d:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
According to kwen2501, NCCL supports up to size_t send counts, so PGNCCL shouldn't restrict it A follow up is to think about whether we should add overflow protection of offset [ghstack-poisoned]
According to kewen2501, NCCL supports up to size_t send counts, so PGNCCL shouldn't restrict it A follow up is to think about whether we should add overflow protection of offset ghstack-source-id: eaad7b16f0303e57a413582f72d3e957817fc4f9 Pull Request resolved: #98368
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.
The change + the plan look good to me. Thanks for the quick fix!
@pytorchbot merge -f "The failure is in trunk and not related to this change" |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
Stack from ghstack (oldest at bottom):
According to @kwen2501, NCCL supports up to size_t send counts, so
PGNCCL shouldn't restrict it
A follow up is to think about whether we should add overflow protection
of offset