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

Set logging level to debug for DummyStatsLogger #3662

Merged
merged 1 commit into from
Oct 25, 2017

Conversation

mistercrunch
Copy link
Member

fixes #3660

@coveralls
Copy link

coveralls commented Oct 13, 2017

Coverage Status

Coverage remained the same at 70.113% when pulling 887a497 on mistercrunch:stats_debug into f871634 on apache:master.

@timifasubaa
Copy link
Contributor

lgtm

@rumbin
Copy link
Contributor

rumbin commented Oct 19, 2017

@mistercrunch Are you sure that this fixes #3660? I included your changes in our installation and restarted superset, and these log messages still are flooding the console log. I don't assume that I was supposed to build anything here, as this is only a py file, right?

@xrmx
Copy link
Contributor

xrmx commented Oct 19, 2017

@rumbin you have default log level set to debug, you have to raise it to something less spammy.

@rumbin
Copy link
Contributor

rumbin commented Oct 19, 2017

Well this is embarassing.
I didn't notice that the default LOG_LEVEL is set to DEBUG.

Thanks anyway, @xrmx...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 0.20.5
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[stats_logger] entries flooding the console log
5 participants