-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Clarify opt-einsum usage, fix #127109 #137596
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
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/137596
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 4122cf4 with merge base de4c2a3 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@bmillwood thoughts? |
[ghstack-poisoned]
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.
Sounds good!
|
@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 |
thanks, looks good :) |
Stack from ghstack (oldest at bottom):