-
Notifications
You must be signed in to change notification settings - Fork 25.6k
check fallback_value first. #154493
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
check fallback_value first. #154493
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/154493
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (3 Unrelated Failures)As of commit 3aa8e3f with merge base 7359705 ( BROKEN TRUNK - The following jobs 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. |
cc ezyang SherlockNoMad EikanWang jgong5 wenzhe-nrv [ghstack-poisoned]
This is just a refactor, not a fix for any issue. we do check fallback_value first and early exit instead of checking it not set over and over. cc ezyang SherlockNoMad EikanWang jgong5 wenzhe-nrv [ghstack-poisoned]
@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 |
This is just a refactor, not a fix for any issue. we do check fallback_value first and early exit instead of checking it not set over and over. Pull Request resolved: pytorch#154493 Approved by: https://github.com/bobrenjc93
Stack from ghstack (oldest at bottom):
This is just a refactor, not a fix for any issue.
we do check fallback_value first and early exit instead of checking it not set over and over.
cc @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv