-
Notifications
You must be signed in to change notification settings - Fork 9
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
Support setting direct_running_mode for LocalDirectRunner #65
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #65 +/- ##
=======================================
Coverage 96.46% 96.47%
=======================================
Files 15 15
Lines 509 510 +1
=======================================
+ Hits 491 492 +1
Misses 18 18 ☔ View full report in Codecov by Sentry. |
#66 sets the logging config |
Changing this default would reduce multi-core performance when running locally, so maybe let's hold off for a second. |
Hey Yuvi - going through and attempting to get things aligned and cleaned up in terms of PRs and I'm wondering if maybe we should just accept the default of multi_processing but keep the configurable argument so that it is easier to enable the more debug-friendly multi_threading case? |
This also changes the default local one from multi_processing to multi_threading. The primary use here is to make the logging config from the *runner* be inherited by the *workers* too, which helps with debugging quite a bit.
82c45e7
to
ff36901
Compare
@moradology that sounds like a good way to proceed! |
This also changes the default local one from multi_processing to multi_threading. The primary use here is to make the logging config from the runner be inherited by the workers too, which helps with debugging quite a bit.