Skip to content
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

Closed
wants to merge 2 commits into from

Conversation

wanchaol
Copy link
Contributor

@wanchaol wanchaol commented Apr 5, 2023

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

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]
@pytorch-bot
Copy link

pytorch-bot bot commented Apr 5, 2023

🔗 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 SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 1 Failures

As 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.

@pytorch-bot pytorch-bot bot added the release notes: distributed (c10d) release notes category label Apr 5, 2023
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]
wanchaol added a commit that referenced this pull request Apr 5, 2023
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
Copy link
Contributor

@kwen2501 kwen2501 left a 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!

@wanchaol wanchaol added the ciflow/trunk Trigger trunk jobs on your pull request label Apr 5, 2023
@kwen2501
Copy link
Contributor

kwen2501 commented Apr 5, 2023

@pytorchbot merge -f "The failure is in trunk and not related to this change"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

@kwen2501 kwen2501 added the topic: bug fixes topic category label Apr 5, 2023
@facebook-github-bot facebook-github-bot deleted the gh/wanchaol/283/head branch June 8, 2023 19:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ciflow/trunk Trigger trunk jobs on your pull request Merged release notes: distributed (c10d) release notes category topic: bug fixes topic category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants