Gem not updated with the latest code

[gavingmiller]

Ran across an issue trying to set log level via config/environments/production.rb not being respected by the rails_stdout_logging gem. The code in master is setup to allow this, but you've not updated the gem with this change. Can you please do so? 😃

Thanks for the great work!

Temporary workaround is to set ENV['LOG_LEVEL'] on heroku.

[schneems]

Version 0.0.2 was released with this code change in August: http://rubygems.org/gems/rails_stdout_logging/versions/0.0.2

New installs of rails_12factor and rails_stdout_logging should be getting the correct code.

If not you may need to $ bundle update rails_stdout_logging on your project.

[gavingmiller]

I believe you're incorrect. The code as of August 30 is here and the specific lines in question read as:

def self.log_level
  ([ENV['LOG_LEVEL'].to_s.upcase, "INFO"] & %w[DEBUG INFO WARN ERROR FATAL UNKNOWN]).compact.first
end

There is no reference to the Rails.config, only to the environment log level. The change to resolve this issue occurred on Sept 5th. So the current gem is outdated with what's on master.

[schneems]

I believe you're incorrect

I believe you're correct on that one.

Sorry I mis-understood the reference. This change was merged when I was away for several days at funeral. I forgot to cut a release. I'll look into doing that soon. Thanks for opening the issue! ❤️

[gavingmiller]

No worries. Thanks for looking into it further. 👍

[hone]

Just cut v0.0.3

[schneems]

thanks @hone ❤️ do you even sleep bro?

[hone]

:) I got a few hours in before planning meeting.

On Tue, Oct 8, 2013 at 12:15 PM, Richard Schneeman <notifications@github.com

wrote:

thanks @hone https://github.com/hone [image: ❤️] do you even sleep
bro?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/7#issuecomment-25904461
.