-
Notifications
You must be signed in to change notification settings - Fork 63
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
Honor Logger#level overrides #41
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
What's the perf impact? I assume it's minimal, but it's the only thing that might block this being merged. Can you show it's minimal? |
Yes, it’s minimal:
Benchmarking scriptrequire 'benchmark/ips'
require 'logger'
class Logger
def add_using_method(severity, message = nil, progname = nil)
severity ||= UNKNOWN
if @logdev.nil? or severity < level
return true
end
if progname.nil?
progname = @progname
end
if message.nil?
if block_given?
message = yield
else
message = progname
progname = @progname
end
end
@logdev.write(
format_message(format_severity(severity), Time.now, progname, message))
true
end
end
logger = Logger.new(File.open("/dev/null", "w"))
Benchmark.ips do |x|
x.config :time => 5, :warmup => 2
x.report("ivar") { logger.add(Logger::DEBUG, "Test") }
x.report("method") { logger.add_using_method(Logger::DEBUG, "Test") }
x.compare!
end |
ioquatix
approved these changes
Sep 6, 2019
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.
Change is minimal, doesn't appear to break backwards compatibility, and performance impact is minimal.
I am happy with this. |
This was referenced Sep 11, 2019
georgeclaghorn
added a commit
to rails/rails
that referenced
this pull request
Sep 13, 2019
We prepend a check against the thread-local level to Logger#add, but because it proceeds to check against the thread-global level, only setting a quieter thread-local level works. The quietest of the two wins. Fix by reimplementing #add entirely. It's unfortunate to have to do this, but I've already patched upstream Logger to prefer the level instance method over the @Level instance variable, so we'll be able to avoid touching #add at all in the future. See ruby/logger#41.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We attempt to override
Logger#level
in Rails’s Logger subclass to allow setting a different level per thread (and thus per request). ButLogger#add
checks the new message’s severity against the@level
instance variable, so overriding#level
doesn’t have the intended effect. (We also prepend a check against#level
to#add
, so you can only set the thread-local level greater than or equal to@level
, not less. We’d like to allow setting any thread-local level.)This patch modifies
Logger#add
to check#level
so that third-party loggers can customize how the current level is determined without needing to reimplement#add
or juggle multiple underlying Logger instances.