The Weirdest Error Message in Coding...

[@LowLevelTV]

🔴 LIVE @ lowlevel.tv/live

[@Nadeli0]

I made a library for Java once that had its own set of Exception classes, one of my favorites was when you used delete() on an instance that was running it would throw the exception: "Instance running to fast to catch, cannot eliminate instance: [instance id]"

[@Langlykek]

I love when people see some linux logging and pitch a fit if something like "killing apache children" shows up :D. We had to talk someone off a soapbox on one of those years ago. ITS NOT LITERAL APACHE CHILDREN

[@blarghblargh]

The root of that problem was naming the project "Apache" to begin with (and yeah I know the pun)

[@tomsmith6513]

@@blarghblargh apache children in a native environment, how about that . . .

[@fakeAratPrime]

The weirdest thing I got while learning Java a couple of years ago was "Suspicious List Remove on line x" or something like that.

[@kart_elon_xd]

Making an urgent hotfix commit for production rn.

[@somone799]

Debug logs need more humor in them 😂

[@AlfieLikesComputers]

No they don't.. they really don't... I think it is already easy enough to read, it'll ruin it with some unnecessary text

[@andreasjoannai6441]

0x3E8: SYSTEM_STARTUP_TIMEOUT "The system has taken too long to start. If it attempted to continue, it would have taken a thousand years, perhaps then a thousand more." Actual cause: The system attempted to load a file during the startup process, but when retrieving data from the file, it took too long to receive anything (so the system gave up entirely). This can indicate a possible drive failure.

[@w4439]

normalize this please 😂

[@alexzaslavskis4623]

(vivaldo) VHDL: no spawn error 😅

[@a.squirrel1511]

The best one I've had is "lp1 on fire" in the Linux system log, Slackware, probably Linux 0.99 or 1.0.

PHP expects T_PAAMAYIM_NEKUDOTAYIM

[@ncsredemption8942]

What library was this from?

[@3v1lm4nipul4t0r]

☠️💀