Skip to content

Correctly resolve dispatch keys for PyOperator#96306

Closed
ezyang wants to merge 6 commits intogh/ezyang/1894/basefrom
gh/ezyang/1894/head
Closed

Correctly resolve dispatch keys for PyOperator#96306
ezyang wants to merge 6 commits intogh/ezyang/1894/basefrom
gh/ezyang/1894/head

Conversation

@ezyang
Copy link
Contributor

@ezyang ezyang commented Mar 8, 2023

Stack from ghstack (oldest at bottom):

Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked. Now they work.

Signed-off-by: Edward Z. Yang [email protected]

Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <[email protected]>

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Mar 8, 2023

🔗 Helpful Links

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

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

✅ No Failures

As of commit 787c071:
💚 Looks good so far! There are no failures yet. 💚

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

@ezyang ezyang requested review from angelayi and zou3519 March 8, 2023 15:23
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

[ghstack-poisoned]
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

[ghstack-poisoned]
@ezyang ezyang added release notes: composability release notes category topic: bug fixes topic category labels Mar 8, 2023
Copy link
Contributor

@zou3519 zou3519 left a comment

Choose a reason for hiding this comment

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

LGTM

Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

[ghstack-poisoned]
ezyang added a commit that referenced this pull request Mar 8, 2023
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

ghstack-source-id: 400eaa9
Pull Request resolved: #96306
@albanD albanD removed their request for review March 8, 2023 20:03
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

[ghstack-poisoned]
@ezyang ezyang added the ciflow/trunk Trigger trunk jobs on your pull request label Mar 8, 2023
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

[ghstack-poisoned]
ezyang added a commit that referenced this pull request Mar 8, 2023
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <ezyangmeta.com>

ghstack-source-id: 00f7601
Pull Request resolved: #96306
@ezyang
Copy link
Contributor Author

ezyang commented Mar 9, 2023

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your 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

Advanced Debugging
Check the merge workflow status
here

cyyever pushed a commit to cyyever/pytorch_private that referenced this pull request Mar 12, 2023
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <[email protected]>
Pull Request resolved: pytorch/pytorch#96306
Approved by: https://github.com/Skylion007, https://github.com/zou3519
ydwu4 added a commit to ydwu4/pytorch that referenced this pull request Mar 13, 2023
Previously, we never actually used resolve_key, which meant that
you had to register CPU/CUDA/etc all manually; none of the alias
keys worked.  Now they work.

Signed-off-by: Edward Z. Yang <[email protected]>
Pull Request resolved: pytorch#96306
Approved by: https://github.com/Skylion007, https://github.com/zou3519
pytorchmergebot pushed a commit that referenced this pull request Mar 27, 2023
Ed's previous PRs in stack #96306 fixes #89037, but this PR just removes the original hacky fallthrough.

Pull Request resolved: #96635
Approved by: https://github.com/zhxchen17
@facebook-github-bot facebook-github-bot deleted the gh/ezyang/1894/head branch June 8, 2023 16:55
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: composability release notes category topic: bug fixes topic category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants