From: Tero Tilus <tero@tilus.net>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Strategy for dealing with nil and thread errors
Date: Fri, 21 Jan 2011 08:59:16 +0200 [thread overview]
Message-ID: <1295592790-sup-5869@tilus.net> (raw)
In-Reply-To: <1295563880-sup-5855@ezyang>
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
prev parent reply other threads:[~2011-01-21 8:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 22:57 Edward Z. Yang
2011-01-21 6:46 ` Rich Lane
2011-01-21 6:59 ` Tero Tilus [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1295592790-sup-5869@tilus.net \
--to=tero@tilus.net \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox