-
Notifications
You must be signed in to change notification settings - Fork 404
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
Clean up settings.debug #2612
Clean up settings.debug #2612
Conversation
This pull request was exported from Phabricator. Differential Revision: D65498337 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2612 +/- ##
==========================================
- Coverage 99.98% 99.98% -0.01%
==========================================
Files 196 196
Lines 17372 17359 -13
==========================================
- Hits 17370 17357 -13
Misses 2 2 ☔ View full report in Codecov by Sentry. |
Summary: In the past, `settings.debug` used to supress all `BoTorchWarnings`. Some time ago, we reduced its scope and started surfacing these warnings again. Since then, there are only a couple places where `settings.debug` is used. I was curious how much usage it had left and decided to clean it up completely while at it. Differential Revision: D65498337
3692626
to
30c0fe0
Compare
This pull request was exported from Phabricator. Differential Revision: D65498337 |
Summary: In the past, `settings.debug` used to supress all `BoTorchWarnings`. Some time ago, we reduced its scope and started surfacing these warnings again. Since then, there are only a couple places where `settings.debug` is used. I was curious how much usage it had left and decided to clean it up completely while at it. Differential Revision: D65498337
30c0fe0
to
c0801bd
Compare
This pull request was exported from Phabricator. Differential Revision: D65498337 |
This pull request has been merged in 8b13120. |
Summary: In the past,
settings.debug
used to supress allBoTorchWarnings
. Some time ago, we reduced its scope and started surfacing these warnings again. Since then, there are only a couple places wheresettings.debug
is used. I was curious how much usage it had left and decided to clean it up completely while at it.Differential Revision: D65498337