KEMBAR78
[DTensor] Returned new placements for neg dim in global info by awgu · Pull Request #113922 · pytorch/pytorch · GitHub
Skip to content

Conversation

@pytorch-bot
Copy link

pytorch-bot bot commented Nov 17, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/113922

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 68244cc with merge base 6ed20af (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

Copy link
Collaborator

@wanchaol wanchaol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My feeling is that since we normalized the shard dim for every public API, from_local, distribute_tensor and redistribute, we don't need to do normalize again when computing the global info? maybe we can simply delete this normalization logic

awgu pushed a commit that referenced this pull request Nov 20, 2023
…ith assert in helper"


This is a replacement for #113922. I think we can still leave the check for negative shard dimension in `compute_local_shape_and_global_offset` and replace the normalization logic with an assert. This should provide us a stack trace to see which user-facing API did not normalize the dim as expected.

[ghstack-poisoned]
awgu pushed a commit that referenced this pull request Nov 20, 2023
…lper"


This is a replacement for #113922. I think we can still leave the check for negative shard dimension in `compute_local_shape_and_global_offset` and replace the normalization logic with an assert. This should provide us a stack trace to see which user-facing API did not normalize the dim as expected.

[ghstack-poisoned]
pytorchmergebot pushed a commit that referenced this pull request Nov 21, 2023
This is a replacement for #113922. I think we can still leave the check for negative shard dimension in `compute_local_shape_and_global_offset` and replace the normalization logic with an assert. This should provide us a stack trace to see which user-facing API did not normalize the dim as expected.
Pull Request resolved: #114141
Approved by: https://github.com/wanchaol
ghstack dependencies: #113919, #113924, #114134, #113925, #113930
@awgu awgu closed this Nov 21, 2023
@facebook-github-bot facebook-github-bot deleted the gh/awgu/458/head branch December 22, 2023 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants