From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.229.71 with SMTP id jh7cs231304icb; Fri, 21 Jan 2011 00:18:13 -0800 (PST) Received: by 10.224.45.132 with SMTP id e4mr351571qaf.296.1295597893258; Fri, 21 Jan 2011 00:18:13 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id k9si19129444qct.112.2011.01.21.00.18.12; Fri, 21 Jan 2011 00:18:13 -0800 (PST) Received-SPF: pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-devel-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-devel-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 8EEAE1858375; Fri, 21 Jan 2011 03:18:12 -0500 (EST) Received: from kuovi.tilus.net (kuovi.tilus.net [80.68.89.168]) by rubyforge.org (Postfix) with ESMTP id D828018581B2 for ; Fri, 21 Jan 2011 01:59:17 -0500 (EST) Received: by kuovi.tilus.net (Postfix, from userid 1000) id CB998601A; Fri, 21 Jan 2011 08:59:16 +0200 (EET) From: Tero Tilus To: sup-devel In-reply-to: <1295563880-sup-5855@ezyang> References: <1295563880-sup-5855@ezyang> Date: Fri, 21 Jan 2011 08:59:16 +0200 Message-Id: <1295592790-sup-5869@tilus.net> User-Agent: Sup/git Subject: Re: [sup-devel] Strategy for dealing with nil and thread errors X-BeenThere: sup-devel@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sup developer discussion List-Id: Sup developer discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-devel-bounces@rubyforge.org Errors-To: sup-devel-bounces@rubyforge.org Edward Z. Yang, 2011-01-21 00:57: > Usually the bugs are kind of harmless, so I just shrug, ignore the > UI oddity, reboot our client, and hope it doesn't come back again. Do you report the bugs you encounter? > Sometimes it's really bad, in which case I might need to reload our > index (but usually it goes away after that) or patch the immediate > bit of code Do you send in your patches? > I was curious if other people have had similar experiences. Not anymore. For about a year now I've only managed to make sup spit backtraces only from code I've written myself. > I know threading is fucking hard, and writing code that is robust > against internal corruption (which I assume is the source of nils) > is fucking hard, but I think it's a worthy goal Is there anyone who doesn't? > and I think we should be thinking about ways to help rule out these > errors in the Sup codebase. Do you have any suggestions? Besides the obvious "just try hard!" which I assume all sup contributors already do. -- Tero Tilus ## 050 3635 235 ## http://tero.tilus.net/ _______________________________________________ Sup-devel mailing list Sup-devel@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-devel