Error
We track 22 posts about Error from 13 engineering blogs. Most active: The Daily WTF, SitePoint, The Daily WTF. Latest post: Oct 9, 2026.
Companies writing about Error
Recent posts
Error'd: Fast Quick (opens on the source site)
Matias shared a standard sort of flubstituted fail-merge error'd; not really egregious, just routine. "I am {{emotionType}} to hear this." And another mail-not-merged from Reinier B. "When the package from [SELLER] seemed to be lost in the mail, I was very [EMOTIONAL_STATE] with the refund of [AMOUNT]. I can now buy another [ITEM] instead." Dave A. didn't care for this mail flub, though it's hardly egregious in my opinion. He suggested we just label it with "A short description of snarky comments." "I've_missed_you_too" Willy wrote in response to this earnest email. "Long lasting…
Next.js Chunk Load Error: How to Fix Production Failures (opens on the source site)
Diagnose and resolve intermittent Next.js App Router ChunkLoadError issues in production, from deploy skew and proxy matchers to CDN caching and error boundaries. Continue reading Next.js Chunk Load Error: How to Fix Production Failures on SitePoint.
Error'd: 12345 (opens on the source site)
We have for you this week a full set of the Error'd we most love to hate: the perverse password policy. An anonymous reader drops this, with little to say except to note "Speciaal passwords". Evidently they supplied a password which satisfied each of the five green critera, but still it was rejected. It would be nice to know where this offense originated, Intrepid Michael R. explains "note: Handy is the German term for mobile phone (UK) or cell phone (US)." Sacha R. observes a secret policy at play, saying "Oracle try to do the right thing by showing you the password policy requirements when…
JavaScript Fetch Error Handling: Build a Reusable TypeScript Wrapper (opens on the source site)
Build a reusable TypeScript wrapper for the Fetch API that normalizes network errors, HTTP status codes, timeouts, and JSON parsing into a predictable error hierarchy. Continue reading JavaScript Fetch Error Handling: Build a Reusable TypeScript Wrapper on SitePoint.
Error'd: Said Different (opens on the source site)
I know it's not nice to mock mistranslations, but would you believe we're laughing with them, not at them? In response to recent criticism of the difficulty of identifying precisely what is at issue, two of our readers have chosen to highlight the offending element. Thanks for saving me the trouble!" "Bad Dutch translation, or is't?" asketh Mike V. "I visited the Dutch Dell site https://www.dell.com/nl-nl and noticed the bad translation on the "Accept All" cookies button. Then I visited the UK page on https://www.dell.com/en-uk and was not so sure anymore about the bad translation. Funny…
Error'd: Ai Dios Mio (opens on the source site)
It seems like only yesterday we were mocking the AIs for their limits, and tomorrow they're going to be mocking ours. In the meantime, here's a look back at some humorous moments from the last year or so. "Mathing is hard" wrote Timothy W. "I for one welcome our new AI overlords." "AI is replicating" quipped a clever anon who styled themselves AInonymous. "I don't want AI features on my phone. And yet, I'm now getting not just one, but two AI items on my context menu." "AI is for the birds" chirped The Beast in Black. "Looks like someone's AI tool for image classification needs less of the A…
SNAP payment error detection: how Elastic helps US states beat the FY2028 penalty (opens on the source site)
Elastic ·
Detecting SNAP fraud requires a layered approach, where rules catch what agencies know to look for, machine learning surfaces what rules miss, and conversational investigation helps analysts act on what the data reveals. Elastic delivers all three.
How we AI-updated 1,138 Error-code Docs Pages (opens on the source site)
Twilio ·
How Twilio updated 1,138 error-code docs pages using the OpenAI API, automated quality checks, and human-guided reviews.
Error'd: Unrewarding (opens on the source site)
Some new and some old entries this week, from people who find zero profoundly unrewarding. "A scary blue button from The North Face" warns Dmitry K.. "Northface has just proudly rewarded me with nothing. I am not sure whether I want to try adding such a non-positive amount to my wallet. I am afraid I can trigger a chain reaction that will crash the financial system of the whole world..." "0% Steam discount" advises Renan "As much as I love Final Fantasy, I guess I'll pass on this 0% discount." "Give me my money around zero" demands Reinier B. "The Nederlandse Spoorwegen (Dutch Railways) owe…
Error'd: Good Time (opens on the source site)
Astute readers noticed last week that this editor (that is to say, me) had his own error'd failure to remember what day it was. Thank you for pointing it out promptly, and then proceeding to send in a bunch of examples of other sites calendar failures. Misery loves company! Traveler's travails, from C_Chell "Trying to complete the form on https://www.ihg.com to tell when I plan to arrive at the hotel, I can't complete the form because of this little time problem." "You Have -1 Month(s) To Order!" announces dragoncoder047. "Ah, GradImages... the company that told all graduates that they'd get…
Error'd: Failure, After Failure, After Failure... (opens on the source site)
We have a couple from Foo (AKA Foo) today, include a special text copy-paste Foo shared "I know you usually post image WTFs here, but here's a text output from chromium: [...:ERROR:components/viz/service/display/display.cc:273] Frame latency is negative: -0.18 ms While this issue might be fixed by now, at least on some platforms, I think it's remarkable that someone actually wrote this message without wondering if it ever makes sense ... And also commented "I visited Spain to see the eclipse (which was great BTW). I had heard that temperature may drop during totality, but was surprised by how…
Error'd: Hello, New Mexico! (opens on the source site)
Peter G. shared with us yet another ordering bungled example of. "Should really say "please engage in an Easter egg hunt to find your language"." "Google can't count" claimed Peter S.. It adds up. "Yet another proof that 0=1, this time from Google." "Thanks, Microsoft" groused Ivan "Ever since Microsoft ate university e-mail services worldwide and became responsible for major free software mailing lists, quality of service has been steadily dropping. In order to report delivery problems to Outlook, you need a Microsoft account. You're prevented from creating it at first because of "suspicious…
Error'd: Zero to Zero in 0 seconds (opens on the source site)
"So many zeroes! I'm in." W00H000! Kivi S. "found this ad in the wild. This must be a very large jackpot, look at all those zeroes!" "I knew it!" groused an anonymous cynic. "Yes, SignUpGenius. We all know that SUCCESS is just an illusion." Another anonymous grouch reported "I guess JustWatch has suddenly become a bit precious about their sources" "These boots are made for crashing" thundered Michael R. "PII of the developer have been removed to protect the not so innocent." You can't hide PHP so easily. And again from prolific Michael R. "El Reg has been around for 30+ years and their code…
Next.js error handling: a practical guide (opens on the source site)
Next.js gives developers a structured way to handle errors at every level of an application — from form validation to root-level crashes. Learn how to manage expected errors with return values, catch uncaught exceptions with error boundaries, and set up automatic error reporting in production.
From error-handling to structured concurrency (opens on the source site)
How should we think about error-handling in concurrent programs? In single-threaded programs, we’ve mostly converged on a standard pattern, with a diverse zoo of implementations and concrete patterns. When an error occurs, it is propagated up the stack until we find a stack frame which is prepared to handle it. As we do so, we unwind the stack frames in-order, giving each frame the opportunity to clean up or destroy resources as appropriate.
How to fix osm2pgrouting error ‘relation “__waysXXXX” does not exist’ and speed up the import (opens on the source site)
I don’t seem to have time or energy for long posts these days, but here’s another quick post which might save you some time and frustration. Recently, I’ve been trying to import OpenStreetMap data into a PostGIS database to use with pgRouting. I wanted to import data for the whole of England – which has […]
Workaround for MySQL’s “can’t specify target table for update in FROM clause” Error (opens on the source site)
jOOQ ·
In MySQL, you cannot do this: The UPDATE statement will raise an error as follows: SQL Error [1093] [HY000]: You can’t specify target table ‘t’ for update in FROM clause People have considered this to be a bug in MySQL for ages, as most other RDBMS can do this without any issues, including MySQL clones: … Continue reading Workaround for MySQL’s “can’t specify target table for update in FROM clause” Error →
Emoji error! Using the latest Compose with compileSDK < 34 (opens on the source site)
Blundell's Android Tutorials ·
Wanting to use the latest versions of Compose, but your app compileSdk is falling behind? I’ve been there! If you have a compileSdk 1.5.0 you’ll come across a horrid build error. Let’s fix that! The error is question is this: Compose dependencies with a version > […] The post Emoji error! Using the latest Compose with compileSDK first appeared on Blundell.
Avoid Digital Envelope Routine Error in Node.js (opens on the source site)
Got a weird "digital envelope routine::unsupported" error? Who doesn't? Let's get rid of it. The Error One day I started my node app, and it failed with a nasty-gram: Error: error:0308010C:digital envelope routines::unsupported The Cause Since node 17, OpenSSL 3.0 is supported, which moves algorithmss like MD4 to a legacy status -- the kind of legacy that throws errors on newer versions of Node.js. If you see this error, it's because your on node 17+. Fix 1: Downgrade Easy, use node 16 or older. Fix 2: Use Legacy Option Or use new node with old openssl: unset NODE_OPTIONS export…
QR error correction helps and hinders scanning (opens on the source site)
Error correction sounds good. It means fewer errors, right? When it comes to QR codes, that’ll mean easier scanning for people, surely? It seems like that’s not the whole story. I wondered about this, and couldn’t find an answer, so I did some exploration, and found there’s two factors in tension: the error correction on one hand, and the resulting data density on the other: For fixed data, like a particular URL, it’s easier to read a QR code with lower error correction, but only when there’s minimal damage to the code (like reflections and dirt). Error correction works as advertised when…
JSON Parsing from Scratch in Haskell: Error Reporting—Part 2 (opens on the source site)
In the previous post, we set out to rewrite the JSON parser we wrote in Haskell in an earlier post, to add support for error reporting. The parser was written very naively: if it failed, it returned nothing. You couldn’t tell what the failure was or where it happened. That’s OK for a toy parser but error reporting is an absolute must requirement for all good parsers. In the previous post, we finished writing the basic framework for the same. In this post, we’ll finish adding simple but useful error reporting capability to our JSON parser.
JSON Parsing from Scratch in Haskell: Error Reporting—Part 1 (opens on the source site)
In the previous post we wrote a simple but correct JSON parser in Haskell. The parser was written very naively: if it failed, it returned nothing. You couldn’t tell what the failure was or where it happened. That’s OK for a toy parser but error reporting is an absolute must requirement for all good parsers. So in this post and next post, we’ll add simple but useful error reporting capability to our JSON parser.
Related topics
This page is generated automatically from the engineering blogs we follow. Every post links to its source, where it was published. See all sources.