-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Sssshhhhh dask #226
Sssshhhhh dask #226
Conversation
src/prefect/config.toml
Outdated
@@ -2,6 +2,7 @@ | |||
|
|||
# the location of the user's config file | |||
user_config_path = "$HOME/.prefect/config.toml" | |||
dev_mode = false |
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 have a weak opinion that this should be called "debug" rather than "dev_mode" because I can imagine asking people to set Prefect to "debug" in order to submit proper error reports (with logs) or running remote executions in debug mode.
Also, I didn't know this until just now, but TOML supports root-level args, so my vote is actually to move this key "above" the [general]
section so it becomes accessed as prefect.config.debug
. This has a side benefit that entering debug mode has a really clean env var setting: PREFECT__DEBUG=true
.
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.
Love it, will update
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.
Done
Closes #209 by adding a new
debug
kwarg to theDaskExecutor
. Those dangling streams are not performance related and don't impact results in any way, so this PR silences them for your typical user unless explicitly requested through eitherdebug=True
ordev_mode=True
in your config.dev_mode
might also be a useful construct for other bits of functionality, too.Note: there will still be some logging in the tests, because a raw Client object is created for the fixtures. This is good because it reminds us that they're there.