-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Add option to jl_print_task_backtraces(bool)
to control whether or not to print DONE tasks
#47933
Conversation
This lets you print all live tasks, with less noise in the logs, in case it's been a while since the last GC. In some cases, we are seeing many thousands of DONE Tasks, which greatly increase the noise in the logs, and can overwhelm the DataDog logging.
I kind of just want to change |
Right now it's not very useful but I haven't given up on a task naming scheme; with that it would be possible to tell which task was completed and that could be useful information. For now though, you're right that having done tasks in this list don't really add value. |
I just came back here to say the same thing as Pete. I was thinking about this when brushing my teeth just now, and indeed it seems like it'd be better to just always turn this off, without a parameter. And if we ever find some situation in the future, like named tasks, where we want it again, we could turn it back on or add a param? But I'm open to keeping the param now if you do feel that there's value! But yeah, my gut leans the same as Pete's. @kpamnany: what do you think for a final call? |
Yeah, I think an |
5f7beed
to
d8b0518
Compare
Hokay, per popular consensus, i have switched to a boolean parameter. |
Please take a final look. This should be backported to 1.9, since it is modifying a not-yet-released feature. |
jl_print_task_backtraces_skip_done()
, which skips done tasks.jl_print_task_backtraces(bool)
to control whether or not to print DONE tasks
thanks, merged. |
Add option to `jl_print_task_backtraces(bool)` to control whether or not to print DONE tasks (JuliaLang#47933)
…not to print DONE tasks (#47933) Add option to `jl_print_task_backtraces(bool)` to control whether or not to print DONE tasks This lets you print all live tasks, with less noise in the logs, in case it's been a while since the last GC. In some cases, we are seeing many thousands of DONE Tasks, which greatly increase the noise in the logs, and can overwhelm the DataDog logging. The API now takes a bool, which can allow us to control this setting, letting us print the DONE tasks if the user wants to, but also hide them if desired. (cherry picked from commit 8324512)
Add option to `jl_print_task_backtraces(bool)` to control whether or not to print DONE tasks (JuliaLang#47933)
Add option to `jl_print_task_backtraces(bool)` to control whether or not to print DONE tasks (JuliaLang#47933)
Add option to `jl_print_task_backtraces(bool)` to control whether or not to print DONE tasks (JuliaLang#47933)
This lets you print all live tasks, with less noise in the logs, in case it's been a while since the last GC.
In some cases, we are seeing many thousands of DONE Tasks, which greatly increase the noise in the logs, and can overwhelm the DataDog logging.
This addresses part of the logging issues identified in #47932.
@vilterp and @msagarpatel for review.