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, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, 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 CBFB5211B3 for ; Thu, 29 Nov 2018 19:16:45 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 792CC121549; Fri, 30 Nov 2018 04:16:28 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id CA75C121532 for ; Fri, 30 Nov 2018 04:16:09 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id E5B0E211B3; Thu, 29 Nov 2018 19:16:07 +0000 (UTC) Date: Thu, 29 Nov 2018 19:16:07 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20181129191607.qg7e55tnhxq4f4ek@dcvr> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 90173 Subject: [ruby-core:90173] Re: [Ruby trunk Bug#15356] Rack::Deflater on Rails responds with no data on Ruby 2.6.0 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" zundan@gmail.com wrote: > Thanks! The patch actually fixed the problem. OK, that is surprising... > > So you're saying this is not a new problem... > > First time I noticed this was running a Rails app on `2.6.0-preview1` on Heroku. Since then, I've been trying to see what was going on from time to time but I couldn't figure out how Rails and Rack::Deflater interacts with each other as you wrote. Sorry being slow in reporting it here. I might also have to note that the I do NOT see the problem on `2.5.3`. So 2.6.0-preview1 was back in February; and the non-blocking-by-default change wasn't even proposed, yet. So yes, I'm not confident there's another bug, here. Anyways, testing to revert nonblocking-by-default: https://80x24.org/spew/20181129190533.13377-1-e@80x24.org/raw And will probably commit once I iron out the tests.