From: e@...
Date: 2014-02-18T22:17:47+00:00
Subject: [ruby-core:60838] [ruby-trunk - Feature #9532] [Assigned] Expose	logger monitor

Issue #9532 has been updated by Zachary Scott.

Category set to lib
Status changed from Open to Assigned
Assignee set to Narihiro Nakamura
Target version set to current: 2.2.0

Please note: a number of libraries are using this class: https://github.com/search?l=ruby&q=LogDeviceMutex&ref=cmdform&type=Code

----------------------------------------
Feature #9532: Expose logger monitor
https://bugs.ruby-lang.org/issues/9532#change-45252

* Author: Arthur Neves
* Status: Assigned
* Priority: Normal
* Assignee: Narihiro Nakamura
* Category: lib
* Target version: current: 2.2.0
----------------------------------------
I was wondering if we could do this type of change on the logger class:

https://github.com/arthurnn/ruby/commit/376b9f944948662ac816ad179ae90bc50a2a6c8f

I am proposing this, because if we have access to the mutex, on the logger instance, we would be able to synchronize methods such as, https://github.com/rails/rails/blob/95f5f8167ff86550d7fa9f5f7419cc9b38ef9704/activesupport/lib/active_support/logger_silence.rb#L12 . And make it thread-safe.



-- 
http://bugs.ruby-lang.org/