From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-4.1 required=3.0 tests=AWL,BAYES_00, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id 7D78E1F461 for ; Tue, 23 Jul 2019 15:10:36 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 9A41E120AA4; Wed, 24 Jul 2019 00:10:30 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id D4781120A9A for ; Wed, 24 Jul 2019 00:10:28 +0900 (JST) Received: by filter0014p3iad2.sendgrid.net with SMTP id filter0014p3iad2-13026-5D372366-3D 2019-07-23 15:10:31.001931369 +0000 UTC m=+1713551.910374977 Received: from herokuapp.com (unknown [18.232.94.14]) by ismtpd0068p1mdw1.sendgrid.net (SG) with ESMTP id j510uFmDTmWC0VypF1uw-g for ; Tue, 23 Jul 2019 15:10:31.184 +0000 (UTC) Date: Tue, 23 Jul 2019 15:10:31 +0000 (UTC) From: hsbt@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 69387 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 9532 X-Redmine-Issue-Author: arthurnn X-Redmine-Issue-Assignee: sonots X-Redmine-Sender: hsbt X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?9+ToIm+BmphpEzrVEr2fqVDpB0VofQNbgfqsVvtPdY0tN54vfUSqAQHPQN2=2FUH?= =?us-ascii?Q?aMk+QkOKI6oTKWEdL1Hgo3hTPN=2FeC557YUVyRtB?= =?us-ascii?Q?gG++e=2FlO94YcyaQshE6AzLBkm3vInC4e4vSDzbl?= =?us-ascii?Q?9Rwl1i2VshMGZebRuaGOryH36KTf1cTNMTw7NvK?= =?us-ascii?Q?gbeN9gp7MYDBN36lxmcPT7fSxx0CHJG40Ww=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 93887 Subject: [ruby-core:93887] [Ruby master Feature#9532] Expose logger monitor X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #9532 has been updated by hsbt (Hiroshi SHIBATA). Assignee changed from nahi (Hiroshi Nakamura) to sonots (Naotoshi Seo) ---------------------------------------- Feature #9532: Expose logger monitor https://bugs.ruby-lang.org/issues/9532#change-79870 * Author: arthurnn (Arthur Neves) * Status: Feedback * Priority: Normal * Assignee: sonots (Naotoshi Seo) * Target version: ---------------------------------------- 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. -- https://bugs.ruby-lang.org/