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
tracker debug fixes in CLI command + extra logs for Lock #15197
Conversation
@@ -10,6 +10,14 @@ function isTrackerDebugEnabled(ContainerInterface $c) | |||
|
|||
return array( | |||
|
|||
'ini.log.log_writers' => DI\decorate(function ($previous, ContainerInterface $c) { | |||
if (isTrackerDebugEnabled($c)) { | |||
$previous[] = 'screen'; |
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.
Do we really always want to add logging to screen? I reckon many users would have an interest to only log this to file but not screen. Maybe we shouldn't force it? If someone can enable tracker debug in the config file, then they can maybe also add the logging to screen if needed?
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.
ping @diosmosis
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 think this is just for CLI processes, so I'll just add a check for whether in the CLI command as well.
Fix tracker debug when used in a CLI command (like queuedtracking:process).