-
Notifications
You must be signed in to change notification settings - Fork 25.7k
Fix typo in _normalize ref #137079
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
Fix typo in _normalize ref #137079
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/137079
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 d7544d5 with merge base b825848 ( BROKEN TRUNK - The following job failed but were present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
I think this should basically make no difference numerically, but it does have some ramifications on things like CSE. [ghstack-poisoned]
I think this should basically make no difference numerically, but it does have some ramifications on things like CSE. [ghstack-poisoned]
I think this should basically make no difference numerically, but it does have some ramifications on things like CSE. [ghstack-poisoned]
|
@pytorchbot merge -i |
Merge startedYour change will be merged while ignoring the following 1 checks: pull / linux-focal-cuda12.1-py3.10-gcc9-sm86 / test (default, 2, 5, lf.linux.g5.4xlarge.nvidia.gpu) Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
ghstack-source-id: b4ff807 Pull Request resolved: pytorch/pytorch#137079

Stack from ghstack (oldest at bottom):
I think this should basically make no difference numerically, but it does have some ramifications on things like CSE.