Graceful Error Handling?

Running a process to fix the utf-8 support on scirate.com using the unix "screen" command I got the following crash:

Suddenly the Dungeon collapses!! - You die...

Doh!

Tags

More like this

Quantum Loonies Alán Aspuru-Guzik Brissie to Brizzle Cohærence* Complementary Slackness David Deutsch's Blog not exactly in focus Physics and cake Quantized Thoughts Quantum Algorithms Quantum Moxie Quantum Quandries rdv live from Tokyo rose.blog Shtetl-Optimized we don't need no "sticking" room…
Okay, there are some weird plots in science papers out there, but something about this one (which Pak at scirate.com pointed me to), taken from arXiv:0711.1751 "Paleontological Tests: Human-like Intelligence is not a Convergent Feature of Evolution," by Charles H. Lineweaver made me laugh:
Back when I first mentioned the idea, people were kind of down on the idea of SciRate.com, Dave Bacon's project to make a collaborative filter for the arxiv.org prerprint server. Not one to be easily discouraged, Dave has continued to work on it, and it now features papers from all the different…
Some news for those interested in open-source publishing and "Open Science": Dave Bacon is announcing the debut of scirate.com, a sort of social-networking site for physics preprints: The idea came from the observation that while the arxiv is a amazing tool, one of the problems was that the volume…

For some reason, the screen developers added an alternate "nethack" themed message set, and you appear to have it turned on.

You can turn it off with "nethack off" in you .screenrc. Not that the real error message is any more useful for this situation...

I have coded several pieces of software where the catch-all, wtf happened? message was :

I'm sorry Dave, I'm afraid I can't do that.

(Which I know is a misquote.)

By NoAstronomer (not verified) on 19 Jun 2008 #permalink

OK, now you've done it. I'll just have to share a couple of my error-message stories, both from several jobs ago. One customer asked about "about to chunk the butt" which was appearing in his disk-array logs. When asked, the guy who'd written that piece of software said he had no idea why he'd put that in, because he was stoned at the time. He was CTO of my last company, by the way.

The other was my fault. This was cluster software, and in the case of a partition - or, more precisely, discovering that the cluster *had* been partitioned - it was necessary to "kill" members of one group so they could join the other as individuals. The message we used to do this was DGSP - Die, Gravy Sucking Pig. Needless to say, this started appearing in a log file (which wasn't even supposed to be enabled in the shipped code) when a customer was having trouble, so they asked. I told the support engineer, but he figured he couldn't tell the customer what it *really* stood for so he made up "Diagnostic Group Shutdown Partition" instead.

Somebody please stop me before I explain the Tux capacitor.

I remember being quite puzzled the first time I read "printer is on fire" in my syslog.

One from my old mainframe assembler days: someone we worked with who was later fired left behind a message in the OS code (I think this was VS1) that would randomly appear put on the console: "A.M.F.!!" Which I was told by someone meant "audios motherf___er!!"

By JohnQPublic (not verified) on 19 Jun 2008 #permalink

awwww! Brought back the many happy hours I spent playing Nethack (and dying) in grad school (Beckman bears the blame; he introduced me!) when I should've been working on my thesis...