Refactor: extract OperatorArgsKwargsView from parseIValuesToPyArgsKwargs#166368
Refactor: extract OperatorArgsKwargsView from parseIValuesToPyArgsKwargs#166368swolchok wants to merge 11 commits intogh/swolchok/860/basefrom
Conversation
Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/166368
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit b254708 with merge base 84776e1 ( UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
…rom parseIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…ToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…act OperatorArgsKwargsView from parseIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
|
noting for reviewers that CI is currently green |
…xtract OperatorArgsKwargsView from parseIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…ToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…. fix our "upcall" from Python to DTensor dispatch key to be an explicit redispatch so that the preceding fix doesn't break it. on "Refactor: extract OperatorArgsKwargsView from parseIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…rseIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…peratorArgsKwargsView from parseIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…eIValuesToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
…ToPyArgsKwargs" Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) [ghstack-poisoned]
albanD
left a comment
There was a problem hiding this comment.
nit on the comment.
But if CI Is happy, I'm happy!
| // ^- kwarg_only_start | ||
| // ^- positional_default_start | ||
| // ^- 0 | ||
| int64_t positional_default_start_; |
There was a problem hiding this comment.
Why is this in the middle of the existing comment?
There was a problem hiding this comment.
I intentionally broke it up into two comments: one comment explaining the member variables of OperatorArgsKwargsView and another one explaining what's going on in the constructor.
|
@pytorchbot merge |
Merge startedYour 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 |
Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) ghstack-source-id: 08381e1 Pull Request resolved: pytorch/pytorch#166368
Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s). Testing: python test/test_python_dispatch.py (broke during development, seems to work now) ghstack-source-id: 45a3f63 Pull Request resolved: pytorch/pytorch#166368
Stack from ghstack (oldest at bottom):
DTensor.__torch_dispatch__#167051Intended to make it easier to reuse this logic for processing operator arguments as IValues in following PR(s).
Testing: python test/test_python_dispatch.py (broke during development, seems to work now)