we say that making mistakes is human. but when they do happen, we’re quick to point fingers and hope we’re not somehow held responsible.
why is this?
'being wrong’ & ‘mistakes were made (but not by me)’ explore error in all its glory - ranging from funny to grotesque & bewildering to outrageous
full review: https://idealistatheart.com/being-wrong-mistakes-were-made/
Instagram 'Error' Turned Reels into Scroll of Murder, Gore, and Violence — https://www.404media.co/instagram-error-turned-reels-into-neverending-scroll-of-murder-gore-and-violence/
#HackerNews #Instagram #Error #Reels #Violence #Gore #SocialMedia
@knittingknots2 If only we could delete the massive #error that is #ElonMusk 
If one's surname happens to be "Null", expect it to cause havoc with computer systems, as with one unlucky woman... https://mindsconnect.jcink.net/index.php?showtopic=1016&view=getnewpost #computing #database #error #name #tech
Anyone else think of this #loz reference for today's #pixel_dailies ? Sometimes when I'm coding I mutter to myself "I am #error" @pixel_dailies
The old and the new #mechanism - part 2
- Explanation attempts for the understanding of the #reductionistic and #positivistic world view -
In this 2nd part of the article, in my opinion, the #complexity of #biological #systems is taken into account and in this respect the #mereological #fallacy in the old #mechanistic #world #view, that the whole is always more than the sum of its parts, is referred to as a #construction #error in #reductionism.
More at: https://philosophies.de/index.php/2022/01/07/der-alte-und-der-neue-mechanismus-2/
@stux @404mediaco bloody lazy programming, just stick in a #call_lib #404 anytime you want rather than going to the #error #line. Bugs (ha ha) the beejesus out of me!
Bolton Walk-In Clinic in Ontario: lock down your backup already!
DataBreaches hates reporting on an incident when the entity has not yet secured misconfigured storage, but after four months of futile efforts to get a Canadian clinic to respond to responsible disclosures, maybe publication will help get them off the dime.
Do any personal injury lawyers in Ontario, Canada, or folks in the Information and Privacy Commissioner of Ontario follow me? Maybe they can get something done.
Read more at:
https://databreaches.net/2024/12/03/bolton-walk-in-clinic-in-ontario-lock-down-your-backup-already/
#misconfiguration #error #healthsec #dataleak #databreach #exposure #incidentresponse
#DontCallMeHoney
What is on this picture?
a. Current state of old routers your company wouldn't replace because of cost cutting.
b. That server with critical service and eternal uptime, not upgraded so long repositories don't exist now.
c. K8s pod stuck in "Terminating" state.
d. Effect of running code written with ChatGPT.
e. That Windows update you delayed for a year, afraid of some failure, but now it exploded more effectively.
f. Everything mentioned above.
@encthenet I don’t know who added those lines, but the one in malloc.h is really annoying. One of the SPEC2006 benchmarks has a configure script that looks for malloc.h and includes it if it exists (in addition to stdlib.h). On FreeBSD, it then fails to build and tells you to include stdlib.h. The program does already and includes malloc.h only because it exists. As I recall, the file has nothing except a #error line telling you not to include it.
Either delete the files or make them work. Don’t provide them and have them not work.
Lol va_start(3) (https://man.freebsd.org/cgi/man.cgi?query=va_start&apropos=0&sektion=3&manpath=FreeBSD+15.0-CURRENT&arch=default&format=html):
> A backward compatible version can be found in the include file <varargs.h>.
Looks at `varargs.h` (https://cgit.freebsd.org/src/tree/include/varargs.h):
```
#error "Change your code to use <stdarg.h> instead."
```
Hmm.. Guess not.
The #cinema website threw me in a loop. I logged in, picked a movie, room, & show time, which sent me back to the #login interface. Rinse repeat. I could see a seat plan with lots of available seats, but no prices. No purchase without login.
Then we tried to log in using the Google login option. "Google is not connected to a #Cineplex Connect Account" was the stubborn #error message there.
We never got to buy tickets for #Joker but watched a different #movie at home from a USB stick. 3/3
Something wrong with this mouse! 
% #joke #Blasphemy #Shame #DoNotTouch #Heresy #NotAcceptable #ERROR #AnErrorOccurred #WTF #OMG #commodore #NotPossible #Prohibited #amiga #A500 #atari #DF0 #DF1 #Floppy #Disk #Drive #FDD #retrocomputer #retrogaming #80s #90s #Geek
This sounds like it could be a hardware issue - memory corruption. That doesn't have to be actual bad DRAM; it can be overheating CPU, or bad microcode, or oxidized memory contacts, or flaky power supply, or a hundred other things.
Where is this container running? On your own hardware? Have you tried replicating this on a different machine?
My biggest difficulty with linkers is… understanding their errors! I know I'm not alone.
That's why `weld` must be exemplary on errors, period.
Please welcome `weld-errors`, https://github.com/Hywan/weld/compare/b7fde2dbf9fb523dccb041063bfd030967f5e814...4a41bd666c6dc8b76a59bf7c127247312e84127e.
What's new?
* Any error contains a code, a (formatted) message, and a help message,
* `weld` pretty prints those errors,
* `weld --explain <error_code>` gives detailed diagnostics,
* Automatic awesome documentation.
See the screenshots.
