| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | [Active Support] `rubocop -a --only Layout/EmptyLineAfterMagicComment` | Koichi ITO | 2017-07-11 | 1 | -0/+1 |
| | | |||||
| * | Use frozen-string-literal in ActiveSupport | Kir Shatrov | 2017-07-09 | 1 | -0/+1 |
| | | |||||
| * | [Active Support] require => require_relative | Akira Matsuda | 2017-07-01 | 1 | -2/+2 |
| | | |||||
| * | `Broadcast#silence` breaks custom loggers that does not include `LoggerSilence`. | Guo Xiang Tan | 2016-10-24 | 1 | -2/+2 |
| | | |||||
| * | applies new string literal convention in activesupport/lib | Xavier Noria | 2016-08-06 | 1 | -3/+3 |
| | | | | | | The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default. | ||||
| * | Make sure the yielded variable is the logger | Rafael Mendonça França | 2016-06-10 | 1 | -2/+2 |
| | | |||||
| * | Broadcast #silence on logger. Rewrite tests. | Kevin McPhillips | 2016-06-09 | 1 | -0/+18 |
| | | |||||
| * | Fix logger silencing for broadcasted loggers | Piotr Jakubowski | 2016-02-11 | 1 | -0/+7 |
| | | | | | | | | | | | | Fix #23609 Commit 629efb6 introduced thread safety to logger silencing but it didn't take into account the fact that the logger can be extended with broadcasting to other logger. This commit introduces local_level to broadcasting Module which enables broadcasted loggers to be properly silenced. | ||||
| * | Remove unused instance variable | schneems | 2016-01-06 | 1 | -1/+0 |
| | | |||||
| * | [close #22917] Don't output to `STDOUT` twice | schneems | 2016-01-06 | 1 | -1/+11 |
| | | | | | | | | | | | | | | | When `rails console` or `rails server` are used along with a logger set to output to `STDOUT` then the contents will show up twice. This happens because the logger is extended with `ActiveSupportLogger.broadcast` with a destination of STDOUT even if it is already outputting to `STDOUT`. Previously PR #22592 attempted to fix this issue, but it ended up causing NoMethodErrors. A better approach than relying on adding a method and flow control is to inspect the log destination directly. For this `ActiveSupport::Logger.logger_outputs_to?` was introduced ```ruby logger = Logger.new(STDOUT) ActiveSupport::Logger.logger_outputs_to?(logger, STDOUT) # => true ``` To accomplish this we must look inside of an instance variable of standard lib's Logger `@logdev`. There is a related Ruby proposal to expose this method in a standard way: https://bugs.ruby-lang.org/issues/11955 | ||||
| * | Revert "Add Logger option to disable message broadcasts" | schneems | 2016-01-05 | 1 | -12/+3 |
| | | | | | This reverts related commits due to #22917. | ||||
| * | Removed extra "the" in the documentation of `broadcast_message` [ci skip] | Prathamesh Sonpatki | 2015-12-28 | 1 | -1/+1 |
| | | |||||
| * | Merge pull request #22771 from nwjsmith/document-broadcast-messages | Eileen M. Uchitelle | 2015-12-27 | 1 | -1/+9 |
| |\ | | | | | Document `Logger#broadcast_messages` option | ||||
| | * | Document `Logger#broadcast_messages` option | Nate Smith | 2015-12-23 | 1 | -1/+9 |
| | | | |||||
| * | | Fixes LoggerSilence#silence threadsafety | Carl P. Corliss | 2015-12-23 | 1 | -0/+14 |
| |/ | | | | | | | - uses instance defined level if no custom local log level defined - Keeps track of local log level per [ thread + object-instance ] - prevents memory leakage by removing local level hash key/value on #silence method exit - avoids the use of Thread local variables | ||||
| * | Add Logger option to disable message broadcasts | Nate Smith | 2015-12-16 | 1 | -3/+5 |
| | | | | | | | | | | When setting the Rails logger to log to STDOUT, it would broadcast the log twice in development. This adds a setting that will prevent messages from being broadcast to multiple logs, while still allowing calls to `#close`, `#level=`, `#progname=`, and `#formatter=` to be broadcasted. Fixes #14769, #11415 | ||||
| * | Remove deprecated cattr_* requires | Genadi Samokovarov | 2013-12-03 | 1 | -1/+1 |
| | | |||||
| * | Revert "Make sure that ActiveSupport::Logger includes the Logger extensions ↵ | David Heinemeier Hansson | 2012-12-21 | 1 | -1/+3 |
| | | | | | | | from core_ext/logger" (some confusion over deprecation) This reverts commit d00f568a83a5159ed93618b1081bd17858536d1c. | ||||
| * | Make sure that ActiveSupport::Logger includes the Logger extensions from ↵ | David Heinemeier Hansson | 2012-12-21 | 1 | -3/+1 |
| | | | | | core_ext/logger | ||||
| * | Add ActiveSupport::Logger#silence that works the same as the old ↵ | David Heinemeier Hansson | 2012-12-21 | 1 | -0/+4 |
| | | | | | Logger#silence extension | ||||
| * | update AS docs [ci skip] | Francesco Rodriguez | 2012-09-17 | 1 | -1/+1 |
| | | |||||
| * | pushed broadcasting down to a module | Aaron Patterson | 2012-01-20 | 1 | -46/+34 |
| | | |||||
| * | made the broadcast logger quack more like a logger | Aaron Patterson | 2012-01-20 | 1 | -0/+24 |
| | | |||||
| * | add a broadcasting logger so we can split logs | Aaron Patterson | 2012-01-20 | 1 | -0/+23 |
| | | |||||
| * | * BufferedLogger is deprecated. Use ActiveSupport::Logger, or the logger | Aaron Patterson | 2011-12-19 | 1 | -0/+18 |
| from Ruby stdlib. | |||||
 |
index : rails.git | |
| Mirror of official rails repo with custom fixes. | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |