-
Notifications
You must be signed in to change notification settings - Fork 24.2k
change guard_or impl for better perf and simplicity #153674
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
base: gh/laithsakka/181/base
Are you sure you want to change the base?
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/153674
Note: Links to docs will display an error until the docs builds have been completed. ❌ 13 New Failures, 2 Unrelated FailuresAs of commit 91c8ec1 with merge base 8ac82a1 ( NEW FAILURES - The following jobs have failed:
FLAKY - The following job failed but was likely due to flakiness present on trunk:
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. |
@@ -2848,7 +2848,7 @@ def func(a, b): | |||
else: | |||
return b * 20 | |||
|
|||
# call with guarding. | |||
# eager. |
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.
i'm not sure how helpful this comment is, it seems self evident from the code?
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.
overall looks reasonable to me, back to you for test failures
Stack from ghstack (oldest at bottom):
PR time benchmarks has been showing regressions as we move to guard_or_false, reason is that prev implementation do not cache.
This new approach will propagate the fallback value to eval and return it. allowing eval to cache and reducing scamming logs and complexity.
cc @ezyang @SherlockNoMad @EikanWang @jgong5 @wenzhe-nrv