From: "Edward Z. Yang" <ezyang@MIT.EDU>
To: sup-devel <sup-devel@rubyforge.org>
Subject: [sup-devel] Strategy for dealing with nil and thread errors
Date: Thu, 20 Jan 2011 17:57:22 -0500 [thread overview]
Message-ID: <1295563880-sup-5855@ezyang> (raw)
My experience for having run Sup for some appreciable amount of time includes
running into a few Sup exceptions where 'the wrong id is called on some object'
or we attempt to access a field that doesn't exist on nil. I also have run
into any number of race condition style bugs with respect to threading and the
user interface.
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. 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 that is complaining and hope
I have encouraged some silent corruption.
I was curious if other people have had similar experiences. 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 and I think we should be thinking about ways to help rule out these errors
in the Sup codebase.
Cheers,
Edward
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next reply other threads:[~2011-01-20 23:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 22:57 Edward Z. Yang [this message]
2011-01-21 6:46 ` Rich Lane
2011-01-21 6:59 ` Tero Tilus
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=1295563880-sup-5855@ezyang \
--to=ezyang@mit.edu \
--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