Skip to content
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

[BUG] - "None" outputted to stdout many times with no benefit? #105

Closed
n1nj4888 opened this issue Feb 13, 2019 · 1 comment
Closed

[BUG] - "None" outputted to stdout many times with no benefit? #105

n1nj4888 opened this issue Feb 13, 2019 · 1 comment
Labels
bug Something isn't working in-next-release In the next release

Comments

@n1nj4888
Copy link

n1nj4888 commented Feb 13, 2019

Describe the bug
The single word "None" is outputted to stdout many times (appears to be around the same time the Tautilli job runs with no apparent benefit?

2019-02-13 09:23:29 stdout None
2019-02-13 09:23:29 stdout None
2019-02-13 09:23:29 stdout None
2019-02-13 09:23:29 stdout None
2019-02-13 09:23:21 stdout 2019-02-13 09:23:21 : INFO : init : Running job Every 30 seconds do put(<bound method TautulliAPI.get_activity of >) (last run: 2019-02-13 09:22:50, next run: 2019-02-13 09:23:20)
2019-02-13 09:23:21 stdout 2019-02-13 09:23:21 : INFO : init : Running job Every 30 seconds do put(<bound method TautulliAPI.get_activity of >) (last run: 2019-02-13 09:22:50, next run: 2019-02-13 09:23:20)
2019-02-13 09:23:21 stdout None
2019-02-13 09:23:21 stdout None
2019-02-13 09:23:20 stdout None

Also, and this maybe considered a feature request if the functionality does not already exist, is it possible to configure some level of logging so that the "Running job Every ..." lines are not constantly output to the stdout logs? For example, these could be output if logging is set to DEBUG but not output if logging set to ERROR?

To Reproduce
Steps to reproduce the behavior:

  1. Simply check the stdout / container logs and the "None" lines are displayed frequently

Expected behavior
The "None" lines should not be output to Stdout since they offer no benefit or could be configured to not output to stdout with logging levels.

Environment (please complete the following information):

  • OS: Docker (17.05.0-ce) running on Synology
  • Version: v1.6.4-master
@n1nj4888 n1nj4888 added the awaiting-triage Request awaiting triage label Feb 13, 2019
@samwiseg0 samwiseg0 added bug Something isn't working in-next-release In the next release and removed awaiting-triage Request awaiting triage labels Mar 11, 2019
@samwiseg0
Copy link
Member

Fixed in next release. f5c4147

@Boerderij Boerderij locked and limited conversation to collaborators Mar 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working in-next-release In the next release
Projects
None yet
Development

No branches or pull requests

2 participants