instead of built-in custom test library https://github.com/ruby/logger/tree/master/test/lib.

with redefinition of Logger::VERSION

# - Timezone.

#   "%s, [%s #%d] %5s -- %s: %s\n"
#
# where the values to be formatted are:
#
# - \Severity (one letter). %s
# - Timestamp.              %s
# - Timezone.               %d (this one is actually process id)
# - \Severity (word).       %5s
# - Program name.           %s
# - Message.                %s

ref:

When using the formatter and the logger at a UNKNOWN level, the pre-set message string that is passed through to the proc is ANY instead of UNKNOWN

For all other logging levels the message is correct.

Couldn't find where this was generated in the source code, but advise either changing the message pre-set (Patch tweak), or altering the severity level (Major tweak)

EDIT: https://github.com/ruby/logger/blob/master/test/logger/test_logger.rb#L287 - This appears to be an error in the tests here, which looks like it's expecting the string "ANY"

It's hard for anyone viewing this repository to find documentation about how to use the library. It would be good if we could publish the docs from rdoc, like what rake is doing: https://ruby.github.io/rake.

The lib/logger/ directory is missing in the 1.4.0 rubygems release. It’s present in the 1.4.0 GitHub release.

Traceback (most recent call last):
        9: from /rubygems/bin/nanoc:23:in `<main>'
        8: from /rubygems/bin/nanoc:23:in `load'
        7: from /rubygems/gems/nanoc-4.11.9/bin/nanoc:4:in `<top (required)>'
        6: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
        5: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
        4: from /rubygems/gems/nanoc-4.11.9/lib/nanoc.rb:42:in `<top (required)>'
        3: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
        2: from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in `require'
        1: from /rubygems/gems/logger-1.4.0/lib/logger.rb:15:in `<top (required)>'
/rubygems/gems/logger-1.4.0/lib/logger.rb:15:in `require_relative': cannot load such file -- /rubygems/gems/logger-1.4.0/lib/logger/version (LoadError)

It's a little bit inconvenient to write logger.level = Logger::DEBUG. It also means that the API can't be entirely replaced without reusing the values for logger.level exactly as defined by Logger. It would be nice if we could have methods for changing log level, e.g. logger.debug! which changes the log level to Logger::DEBUG and so on for other log levels.

If you create a file with user permissions but then run logger under root the file rotate will not preserve these permissions causing access issues.

% ls -al log.log 
-rw-r--r--  1 reginaldsmith  staff  0 23 Sep 11:17 log.log
% rvmsudo irb
2.7.2 :001 > require "logger"
 => true 
2.7.2 :004 > puts File.stat("log.log").uid
502
 => nil 
2.7.2 :005 > log = File.open("log.log", "a")
 => #<File:log.log> 
2.7.2 :006 > logger = Logger.new(log, "everytime")
 => #<Logger:0x00007fd7cfbc5ee0 @level=0, @progname=nil, @default_formatter=#<Logger::Formatter:0x00007fd7cfbc5eb8 @datetime_format=nil>, @formatte... 
2.7.2 :007 > logger.info "hello"
 => true 
2.7.2 :008 > puts File.stat("log.log").uid
0 
2.7.2 :010 > exit
% ls -al log.log
-rw-r--r--  1 root  staff  123 23 Sep 11:20 log.log
% irb
2.7.2 :001 > require "logger"
 => true 
2.7.2 :002 > log = File.open("log.log", "a")
Errno::EACCES (Permission denied @ rb_sysopen - log.log)
>

Hi, Sidekiq allows users to enable logging per-job so you can do this:

SomeJob.set(log_level: :debug).perform_async(123)

This requires a thread-local log level. I have a ::Logger monkeypatch to enable this feature. Would you like me to create a PR to upstream it? This would allow the user to do something like:

log = ::Logger.new(STDOUT, level: Logger::INFO)
log.debug("Not logged")

Thread.new do
  log.at_level(Logger::DEBUG) do
    log.debug("Logged")
  end
end.join

log.debug("Not logged")

https://github.com/mperham/sidekiq/blob/c12c8b567fcf3357bbd8b82a7d8651ddd7cc30a3/lib/sidekiq/logger.rb#L25-L73

Logger.new fails if shift_age is a symbol.

Error:

irb(main):003:0> Logger.new('a.log', :daily)
ArgumentError (invalid :shift_age :daily, should be daily, weekly, monthly, or everytime)

Environment:

$ bundle list
Gems included by the bundle:
  * bundler (2.0.2)
  * logger (1.4.2)

Expected behavior (My suggestion for design change):

Logger.new('a.log', :daily) works as well as Logger.new('a.log', 'daily').

I can create this file:

require 'logger'
z = Logger.new STDOUT
z.info 'abcde'
z.warn 'abcde'
z.error 'abcde'

but it outputs in black and white. Is color an option?

lib/logger.rb line 269 has broken link:

{level}[Logger.html#attribute-i-level]:

Getting some errors with the logger gem when executing

logger = Logger.new($stdout)
logger.info 'test'

  "errorMessage": "undefined method `[]' for nil:NilClass",
  "errorType": "Function<NoMethodError>",
  "stackTrace": [
    "/var/task/vendor/bundle/ruby/3.2.0/gems/logger-1.6.0/lib/logger.rb:384:in `level'",
    "/var/task/vendor/bundle/ruby/3.2.0/gems/logger-1.6.0/lib/logger.rb:653:in `add'",
    "/var/task/vendor/bundle/ruby/3.2.0/gems/logger-1.6.0/lib/logger.rb:697:in `info'",

error does not appear when using version 1.5.3 of the gem

v1.5.3...v1.6.0

For some reason it looks like the initialize function is not being triggered and thus @level_override is never set to {}

There are undocumented versions not in the changelog. If you want a native English speaker, I would be glad to volunteer.

When Using JRuby 9.3.0.0 in Windows this error occurs.
Reproduction steps:

1) Test script:
`test_logger.rb

logger = Logger.new("D:/log.txt", 5, 1024)
  
150.times do |i|
  logger.info i
end

2) run script:
The easiest way to run JRuby in windows would be installing Java 11 and downloading jruby-complete-9.3.0.0.jar, then run:

D:\>java -jar jruby-complete-9.3.0.0.jar test_logger.rb

3) Console output:
log rotation inter-process lock failed. D:\log.txt -> D:\log.txt.0: The process cannot access the file because it is being used by another process.
log writing failed. closed stream
log shifting failed. closed stream
log writing failed. closed stream
log shifting failed. closed stream
...

4) Cause:
The issue occurs due JRuby returns java for RUBY_PLATFORM when loading the method lock_shift_log

This code correctly sets @shift_age to 7 and @shift_size to 1048576

Logger::LogDevice.new(@filename)

This code will end up with those instance variables set to nil

logger = Logger::LogDevice.new(STDERR)
logger.reopen(@filename)

This could be fixed in LogDevice#initialize by setting the defaults outside of the if @filename condition, or repeating the logic in the LogDevice#reopen.

It would also make sense, though, if you can update the output to be able to also change those values if desired. This could be done by adding an attr_writer for them.

The best course of action would be to support adding/changing the values when a new output is specified. I'm adding a PR with my recommendation.

My specific use case involves a library I'm using instantiating a logger instance for me with STDOUT, and I want to change the output to a file with useful shift values.