Re: [sup-devel] Strategy for dealing with nil and thread errors

[Tero Tilus <tero@tilus.net>]

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