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

Fix log_level handling in <system>. fix #1499 #1501

Merged
merged 2 commits into from
Mar 15, 2017

Conversation

repeatedly
Copy link
Member

Regression of #1398

@repeatedly
Copy link
Member Author

@tagomoris Could you check this?

@repeatedly repeatedly added bug Something isn't working v0.14 labels Mar 14, 2017
Copy link
Member

@tagomoris tagomoris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Totally, LGTM.
I added a comment for trivial coding problem.

# info level can't be specified via command line option.
# log_level is info here, it is default value and <system>'s log_level should be applied if exists.
if ll_value != Fluent::Log::LEVEL_INFO
system.send("log_level=", ll_value)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be system.log_level = ll_value. No reason to call #send.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are right. Will change.

@repeatedly repeatedly merged commit 092ea33 into master Mar 15, 2017
@repeatedly repeatedly deleted the fix-system-log-level-handling branch March 15, 2017 08:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v0.14
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants