Was testing a piece open source java script tool this morning and I knew i was doing something I should and got an error. Instead of seeing "error" I got

"nigga please".

I love open source.

9/18/2006 10:36:14 AM

nice

9/18/2006 10:43:20 AM

my buddy put one into a program that he was writing that said "oh shit".

this was at SAS.

it made it to the testors before he remembered it. it was a really obscure message that no one would've ever seen had it not been going through test cases.

[Edited on September 18, 2006 at 10:44 AM. Reason : *]

9/18/2006 10:44:35 AM

oh for those that were interested I was trying to use a SQL injection attack in a field.

9/18/2006 10:48:32 AM

i laffed

9/18/2006 11:26:13 AM

OH SHIT! Internal Server Error

9/18/2006 11:30:17 AM

^^^ that makes it funny

[Edited on September 18, 2006 at 11:30 AM. Reason : ]

9/18/2006 11:30:38 AM

lol, Raige always brings the real-world funny to Tech Talk, gg man

9/18/2006 2:27:35 PM

got this one today

9/26/2008 11:05:13 AM

I got a pretty good one in my photo gallery, but all I get today is

OH SHIT, INTERNAL SERVER ERROR!!!

9/26/2008 11:10:42 AM

Quote :

"my buddy put one into a program that he was writing that said "oh shit". this was at SAS. it made it to the testors before he remembered it. it was a really obscure message that no one would've ever seen had it not been going through test cases."

hah, i actually heard about that

9/26/2008 11:57:33 AM

i too have gotten a "Catastrophic failure"

catastrophic is not generally a word you want to pair with failure

9/26/2008 1:47:59 PM

at least it's just code

9/26/2008 2:45:02 PM

mine wasn't from visual studio

screen cap got lost in the purge

9/26/2008 3:09:49 PM

my coworker had this happen



[Edited on September 26, 2008 at 3:11 PM. Reason : Ø]

9/26/2008 3:11:03 PM

The world is saved yet again!

9/26/2008 5:09:46 PM

god I wish I could show you guys the shit developers put on phones when we don't hand-hold them

9/26/2008 6:38:57 PM

BATLEARN. lol

9/26/2008 6:53:01 PM

^^You can

9/26/2008 6:54:45 PM

11/13/2008 1:59:11 PM

^i lol'd for real

11/13/2008 2:24:13 PM

^^That's getting forwarded internally hahahahah

11/13/2008 2:35:21 PM

^^^lmao

11/13/2008 9:11:32 PM

talk about dependency hell

11/13/2008 9:40:28 PM

Best one i ever saw (and i wish i still had the screen cap) was something like this.


Helper function failed: invalid object name. Call Chris.

11/13/2008 10:16:05 PM

My favorite that I've personally gotten was this little gem I found in Diablo II years ago...



The frown face emoticon makes it, in my opinion.

11/14/2008 12:13:55 AM

I wish that I could find it.

Well to tell a short little story. I used to have a WRT54G v2, and it would be a pain with any online application, so you had to download a homemade bios and flash the bios on the router with it.

Well, sometimes the new builds of the bios's didn't work, and you had to spend a while pushing that black pin in the back of your router for 3 minutes (I swear kids are going to laugh at this one day)

The Error Messages one of the bios update gave me, and I quote:

"UPDATE ARE FAILED"

11/14/2008 12:42:17 AM

Zune 3.1



Setup cannot continue because the install failed, sounds like circular reasoning.

11/19/2008 5:07:36 PM

^I had the same error recently. The new Zune version is awful and only worked when I did a fresh install on a newly configured machine.

11/19/2008 5:36:43 PM

^ and ^^ you should really submit those to MS. People take that shit pretty seriously, problem is almost no one ever actually sends off bug reports.

11/19/2008 8:54:35 PM

11/20/2008 1:41:18 AM

This includes a link to an internal webpage that the customer can't access.

ERROR: Someone tried to free memory that's not currently allocated!
       The free is for address 0xDEADFEED, length -1.

Requested pool: 0x0299374C (pool #422),
   ISA: 16K, OSA: 11K, 0 puddles
   REB: 0x039A2B88

Tips for debugging memory problems may be found on the
SAS Wide Web in

    http://sww.sas.com/pktd/memdebug.html
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
               Note: new address!

NOTE: The following traceback indicates where the problem was detected,
but may or may not be related to the actual problem.

11/20/2008 7:44:23 AM

Quote :

"^ and ^^ you should really submit those to MS. People take that shit pretty seriously, problem is almost no one ever actually sends off bug reports."

it's not the user's responsibility to submit bug reports. would anybody even know where to send it? i don't think most people are under the impression that microsoft would even pay attention to them if they did.

[Edited on November 20, 2008 at 9:11 AM. Reason : ie the users aren't the problem. bad code is the problem]

11/20/2008 9:11:21 AM

Unless it asks me to send a bug report, I don't bother trying to find another way to send it.

11/20/2008 9:27:25 AM

^^^LOL!

[Edited on November 20, 2008 at 9:54 AM. Reason : lol]

11/20/2008 9:54:35 AM

very timely example, on your own application Noen. bug WAS reported, and still hasn't been resolved for 4 years

http://www.codinghorror.com/blog/archives/001189.html

Quote :

"Visual Studio doesn't use the correct font when building Windows applications. Is this a bug or a feature request? Personally, I consider this a bug. I guess Microsoft does too, at least in theory, because it's been in Microsoft's Connect bug tracking system for over four years now. When you build a Windows application, wouldn't you expect it to use the default font of the underlying operating system you're running it on, unless you've explicitly told it otherwise? Well, guess what happens when you create a new form in Visual Studio 2008 and instantiate a label control. Party like it's 1996, folks, because you'll get MS Sans Serif, and you'll like it. That is the default for each new form. Never mind that every new application you build will look like -- let me put this as delicately as I can -- ass. Here's a comparison of a label with the default font, versus one that was explicitly set to the default GUI font. Judging by the applications I've used, most Windows developers couldn't care less about design. That's bad. What's even worse is learning that same design carelessness has shipped in the box with every copy of Visual Studio since 2002. Of course, matters of design are so subjective. If only there were some definitive source we could refer to on the matter of proper Windows GUI font usage. Some sort of reference standard, as it were. Like, say, the top rules for Windows Vista User Experience from Microsoft: 1. Use the Aero Theme and System Font (Segoe UI) 2. Use common controls and common dialogs 3. Use the standard window frame, use glass judiciously There are 12 rules in total, but the rule I'm looking for is right at the top -- applications should use the system font. The hilarity of this list is already sort of self evident, given that I've written an entire post bemoaning the general lack of fit and finish in Windows Vista. I couldn't help but laugh at rule number 12: Reserve time for "fit and finish"! Now there's a rule Microsoft should have taken to heart while developing Windows Vista. Understand this is all coming from a guy who likes Vista. But I digress. Despite the windows forms font behavior in Visual Studio 2008 contradicting rule number one of Microsoft's own design guidelines, this "bug" has gone unfixed for over four years. It has been silently reclassified as a "feature request" and effectively ignored. Nothing's broken, after all: using the wrong font hasn't caused any application crashes or lost productivity. On the other hand, imagine how many BigCorpCo apps have been built since then that violate Microsoft's own design rules for their platform. Either because the developers didn't realize that the app font didn't match the operating system, or because they didn't have the time to write the workaround code necessary to make it do the right thing. Yes, this is a small thing. And I'm sure fixing it wouldn't result in selling an additional umpteen thousand Visual Studio licenses to BigCorpCo, which is why it hasn't happened yet. "

11/20/2008 10:21:19 AM

^ great article/blog

11/20/2008 10:28:24 AM

large BOA display in NYC - woops

12/8/2008 1:06:25 PM

Quote :

"This includes a link to an internal webpage that the customer can't access. ERROR: Someone tried to free memory that's not currently allocated! The free is for address 0xDEADFEED, length -1. Requested pool: 0x0299374C (pool #422), ISA: 16K, OSA: 11K, 0 puddles REB: 0x039A2B88 Tips for debugging memory problems may be found on the SAS Wide Web in http://sww.sas.com/pktd/memdebug.html ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Note: new address! NOTE: The following traceback indicates where the problem was detected, but may or may not be related to the actual problem."

but that page brings you to v7 debugging tips

why would ANYONE still be using v7, haha

oh wait... we do actually, i think it's 6.2

and lol:

Quote :

"Updated: 23 July 1997 "

12/8/2008 1:13:30 PM

^^^^ thats a feature request, not a bug.

If you set the font to one thing and it used a different font, thats a bug.

If you want the default font to be something else, thats a feature request.

Its pretty dumb not to have the default font be the system font, but its not a bug.

[Edited on December 8, 2008 at 1:24 PM. Reason : ^]

12/8/2008 1:24:07 PM

Quote :

"^^^^ that's a feature request design flaw, not a bug."

FTFY

12/8/2008 2:39:27 PM

yea thats probably a better description.

12/8/2008 2:43:08 PM

still not fixed apparently

[Edited on December 9, 2008 at 11:32 PM. Reason : a]

12/9/2008 11:31:52 PM

^Well I can promise people are aware of it, but that's about the extent of what I can do Sorry guys.

The font thing is actually a REALLY silly gripe. If he were writing managed code, which, anyone still writing WinForms should be doing, his forms would be picking up the application environment font, or, the OS environment font. I agree that it would be nice to have it default to whatever the system default is, but really it's not a problem for a very very large majority.

12/9/2008 11:48:32 PM

i did get a laugh out of the "you can now disconnect from the internet" bit.

12/10/2008 11:02:05 AM

bump

10/9/2009 12:16:22 PM

10/9/2009 12:19:19 PM

some of the pixels

10/9/2009 1:14:37 PM

When shutting down a linux workstation I caught the line:

VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...

10/9/2009 1:30:24 PM

^^that's how rdesktop makes your desktop look

10/9/2009 1:50:22 PM