You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bundle exec rails s --no-log-to-stdout does remove the ActiveSupport::Logger but this behaviour is unexpected in my opinion.
If I add a customer logger I expect the Broadcast logger to contain only the sinks that I explicitly included
System configuration
Rails version:
7.1.3 Ruby version:
3.2.2
The text was updated successfully, but these errors were encountered:
Steps to reproduce
Expected behavior
Rails.logger.info("message",foo: "foo", bar: "bar")
Should be able to take variable arguments without throwing an error.
Works as expected in production
Actual behavior
Rails.logger.info("message",foo: "foo", bar: "bar")
In local it fails with
wrong number of arguments (given 2, expected 0..1)
I tracked this down to the fact that in local development,
The Broadcast Logger is instantiated with two sinks even when I want only one sink.
bundle exec rails s --no-log-to-stdout
does remove the ActiveSupport::Logger but this behaviour is unexpected in my opinion.If I add a customer logger I expect the Broadcast logger to contain only the sinks that I explicitly included
System configuration
Rails version:
7.1.3
Ruby version:
3.2.2
The text was updated successfully, but these errors were encountered: