Boring but necessary work... a new type of error handling and logging, allowing for testers to more easily collect any bugged scripts.
#testing #gamedev #errorhandling #indiedev #indiegame
#testing #gamedev #errorhandling #indiedev #indiegame
November 4, 2026 at 5:57 PM
Boring but necessary work... a new type of error handling and logging, allowing for testers to more easily collect any bugged scripts.
#testing #gamedev #errorhandling #indiedev #indiegame
#testing #gamedev #errorhandling #indiedev #indiegame
An Error Just
#programming #debugging #Developerlife #Errormessages #Errorhandling
https://programmerhumor.io/debugging-memes/an-error-just-la9x
#programming #debugging #Developerlife #Errormessages #Errorhandling
https://programmerhumor.io/debugging-memes/an-error-just-la9x
November 1, 2026 at 1:42 PM
Google says normal 404s do not harm healthy pages; use relevant redirects for replacement content and a helpful error page when none exists.
#contentmanagementsystem #errorhandling…
https://www.trickyworld.in/programming/custom-404-pages-google-says-skip-blanket-redirects/?utm_medium=social
#contentmanagementsystem #errorhandling…
https://www.trickyworld.in/programming/custom-404-pages-google-says-skip-blanket-redirects/?utm_medium=social
October 29, 2026 at 12:01 PM
Google says normal 404s do not harm healthy pages; use relevant redirects for replacement content and a helpful error page when none exists.
#contentmanagementsystem #errorhandling…
https://www.trickyworld.in/programming/custom-404-pages-google-says-skip-blanket-redirects/?utm_medium=social
#contentmanagementsystem #errorhandling…
https://www.trickyworld.in/programming/custom-404-pages-google-says-skip-blanket-redirects/?utm_medium=social
Errores silenciosos n8n: el éxito que no era real
Tu workflow dice success y el CRM no recibió nada? Los errores silenciosos n8n se esconden en un 202 mal leído. Mirá cómo detectarlos antes del cliente
#n8n #automatizacion #errorhandling #workflows #crm
Tu workflow dice success y el CRM no recibió nada? Los errores silenciosos n8n se esconden en un 202 mal leído. Mirá cómo detectarlos antes del cliente
#n8n #automatizacion #errorhandling #workflows #crm
Errores silenciosos n8n: el éxito que no era real
Todos los nodos en verde, el CRM vacío. Así se verifican los side effects reales en workflows de n8n para evitar errores silenciosos en producción.
donweb.news
October 28, 2026 at 2:40 AM
Errores silenciosos n8n: el éxito que no era real
Tu workflow dice success y el CRM no recibió nada? Los errores silenciosos n8n se esconden en un 202 mal leído. Mirá cómo detectarlos antes del cliente
#n8n #automatizacion #errorhandling #workflows #crm
Tu workflow dice success y el CRM no recibió nada? Los errores silenciosos n8n se esconden en un 202 mal leído. Mirá cómo detectarlos antes del cliente
#n8n #automatizacion #errorhandling #workflows #crm
Business Process Flow Error: “Participating entity record of stage: X is not valid” (0x80040216) (Dynamics 365 / Dataverse): Scenario Working on a custom multi-entity Business Process Flow (Opportunity → Quote) recently, we ran into this… @nishantranaCRM #BusinessProcess #Dynamics365 #ErrorHandling
Business Process Flow Error: “Participating entity record of stage: X is not valid” (0x80040216) (Dynamics 365 / Dataverse)
Scenario Working on a custom multi-entity Business Process Flow (Opportunity → Quote) recently, we ran into this error while trying to reactivate the process: The BPF (custom_salesprocess) had already traversed several stages — Generate Opportunity → Qualify → Generate Quote → Initiate Deposit/Bank Guarantee → Sales Completion — before landing on PM Completion, which sits … Continue reading "Business Process Flow Error: “Participating entity record of stage: X is not valid” (0x80040216) (Dynamics 365 / Dataverse)"
dlvr.it
October 26, 2026 at 11:37 AM
Business Process Flow Error: “Participating entity record of stage: X is not valid” (0x80040216) (Dynamics 365 / Dataverse): Scenario Working on a custom multi-entity Business Process Flow (Opportunity → Quote) recently, we ran into this… @nishantranaCRM #BusinessProcess #Dynamics365 #ErrorHandling
My favorite kind of modal dialog.
Is it OK?
Or am I accepting that “the error” happened?
#errorhandling
Is it OK?
Or am I accepting that “the error” happened?
#errorhandling
October 13, 2026 at 6:25 PM
My favorite kind of modal dialog.
Is it OK?
Or am I accepting that “the error” happened?
#errorhandling
Is it OK?
Or am I accepting that “the error” happened?
#errorhandling
You found code in a project that seemed like a good fit for your task.
You copied it and replaced the variables with your own.
Oops... Unexpected behavior.
This is how copy-paste errors occur.
pvs-studio.com/en/blog/post...
#Go #Programming #ErrorHandling #Typos
You copied it and replaced the variables with your own.
Oops... Unexpected behavior.
This is how copy-paste errors occur.
pvs-studio.com/en/blog/post...
#Go #Programming #ErrorHandling #Typos
When copy-paste goes wrong: Bugs in structurally isomorphic Go code
pvs-studio.com
October 13, 2026 at 1:18 PM
You found code in a project that seemed like a good fit for your task.
You copied it and replaced the variables with your own.
Oops... Unexpected behavior.
This is how copy-paste errors occur.
pvs-studio.com/en/blog/post...
#Go #Programming #ErrorHandling #Typos
You copied it and replaced the variables with your own.
Oops... Unexpected behavior.
This is how copy-paste errors occur.
pvs-studio.com/en/blog/post...
#Go #Programming #ErrorHandling #Typos
A good error message answers 3 questions:
1️⃣ what happened?
2️⃣ why it matters?
3️⃣ what to do next?
Most only manage the first. Write errors for the fixer, not the author.
#SoftwareEngineering #ErrorHandling
1️⃣ what happened?
2️⃣ why it matters?
3️⃣ what to do next?
Most only manage the first. Write errors for the fixer, not the author.
#SoftwareEngineering #ErrorHandling
October 12, 2026 at 7:02 AM
A good error message answers 3 questions:
1️⃣ what happened?
2️⃣ why it matters?
3️⃣ what to do next?
Most only manage the first. Write errors for the fixer, not the author.
#SoftwareEngineering #ErrorHandling
1️⃣ what happened?
2️⃣ why it matters?
3️⃣ what to do next?
Most only manage the first. Write errors for the fixer, not the author.
#SoftwareEngineering #ErrorHandling
October 7, 2026 at 1:00 AM
PVS-Studio team found an issue in the SqlSugar project: the return value of 'GetString' is called but never used.
#Csharp #Debugging #ErrorHandling
#Csharp #Debugging #ErrorHandling
October 6, 2026 at 2:01 PM
PVS-Studio team found an issue in the SqlSugar project: the return value of 'GetString' is called but never used.
#Csharp #Debugging #ErrorHandling
#Csharp #Debugging #ErrorHandling
Slaide's Themes tab had one message for three different failures: no token, a timeout, an actual 401. All showed 'sign in to keep your themes in the cloud' - even when already signed in. Not sure how those shared a code path. Now it says which one happened, with Retry.
#ErrorHandling
#ErrorHandling
September 12, 2026 at 7:14 PM
Slaide's Themes tab had one message for three different failures: no token, a timeout, an actual 401. All showed 'sign in to keep your themes in the cloud' - even when already signed in. Not sure how those shared a code path. Now it says which one happened, with Retry.
#ErrorHandling
#ErrorHandling
"Linux tip: Tired of Permission denied messages cluttering your find command results? Just add '2>/dev/null' to redirect errors to /dev/null. #Linux #CommandLine #ErrorHandling 🐧💻"
What Does 2>/dev/null Mean in Linux?
2>/dev/null sends a command's error stream into the Linux black hole. What the 2, the >, and /dev/null each do, shown on a real find command.
kodekloud.com
August 30, 2026 at 8:39 AM
"Linux tip: Tired of Permission denied messages cluttering your find command results? Just add '2>/dev/null' to redirect errors to /dev/null. #Linux #CommandLine #ErrorHandling 🐧💻"
Fails For Teapots
#http #programming #backend #api #Errorhandling
https://programmerhumor.io/backend-memes/fails-for-teapots-b490
#http #programming #backend #api #Errorhandling
https://programmerhumor.io/backend-memes/fails-for-teapots-b490
August 22, 2026 at 9:52 PM
📦 logger/errorhandling 1.0.2
Errorhandling extension for PSR-3 compatible loggers
🔗 https://github.com/LoggerEssentials/ErrorHandling
Errorhandling extension for PSR-3 compatible loggers
🔗 https://github.com/LoggerEssentials/ErrorHandling
August 20, 2026 at 11:03 AM
📦 logger/errorhandling 1.0.2
Errorhandling extension for PSR-3 compatible loggers
🔗 https://github.com/LoggerEssentials/ErrorHandling
Errorhandling extension for PSR-3 compatible loggers
🔗 https://github.com/LoggerEssentials/ErrorHandling
In production, it's noise that can clutter the console for users who open devtools. Where do you draw the line? Do you suppress in production only, leave it on everywhere, or conditionally gate it behind a flag? #glitchreplay #errortracking #bugmonitoring #javascript #errorhandling 2/2
August 20, 2026 at 5:21 PM
In production, it's noise that can clutter the console for users who open devtools. Where do you draw the line? Do you suppress in production only, leave it on everywhere, or conditionally gate it behind a flag? #glitchreplay #errortracking #bugmonitoring #javascript #errorhandling 2/2
Rust forces you to decide what happens when a value is missing. Unwrap panics on None, expect panics with your own message, and unwrap_or supplies a fallback that never fails. Choosing upfront keeps error paths explicit instead of hiding crashes. #Rust #ErrorHandling #Programming
August 20, 2026 at 1:26 PM
Rust forces you to decide what happens when a value is missing. Unwrap panics on None, expect panics with your own message, and unwrap_or supplies a fallback that never fails. Choosing upfront keeps error paths explicit instead of hiding crashes. #Rust #ErrorHandling #Programming
Wrapping errors in Go preserves context as they bubble up. fmt Errorf with the percent w verb attaches a cause, and errors Is checks the chain instead of exact matches. Callers get readable messages while the original failure stays inspectable for retries. #Go #ErrorHandling #Programming
August 20, 2026 at 1:27 PM
Wrapping errors in Go preserves context as they bubble up. fmt Errorf with the percent w verb attaches a cause, and errors Is checks the chain instead of exact matches. Callers get readable messages while the original failure stays inspectable for retries. #Go #ErrorHandling #Programming
Error boundaries in React contain crashes to one component instead of a blank page. Wrap feature sections separately, log the failure, show a retry UI, and the rest of the app keeps running. Isolated failure handling is what makes big UIs survive real users. #React #ErrorHandling #Frontend
August 20, 2026 at 12:15 PM
Error boundaries in React contain crashes to one component instead of a blank page. Wrap feature sections separately, log the failure, show a retry UI, and the rest of the app keeps running. Isolated failure handling is what makes big UIs survive real users. #React #ErrorHandling #Frontend
One uncaught exception used to take down the whole page. Error boundaries isolate component failures so a broken widget shows a fallback while the rest of the app keeps working. Wrap features in boundaries, log the error once, and users never see a white screen again. #React #ErrorHandling #Frontend
August 20, 2026 at 12:30 PM
One uncaught exception used to take down the whole page. Error boundaries isolate component failures so a broken widget shows a fallback while the rest of the app keeps working. Wrap features in boundaries, log the error once, and users never see a white screen again. #React #ErrorHandling #Frontend
Go error values read like a checklist, not a complaint. Each function tells you exactly where it failed, wrapping keeps the full chain, and errors.Is lets callers match the cause without string parsing. No stack traces to hunt, just a typed path from failure to fix. #Go #ErrorHandling #Backend
August 20, 2026 at 12:23 PM
Go error values read like a checklist, not a complaint. Each function tells you exactly where it failed, wrapping keeps the full chain, and errors.Is lets callers match the cause without string parsing. No stack traces to hunt, just a typed path from failure to fix. #Go #ErrorHandling #Backend
The Rust error handling debate never ends because every solution optimizes something different. Result chains are explicit but verbose, exceptions style is terse but implicit. Pick a pattern per crate, document it, and stop rewriting it every new hire. #Rust #ErrorHandling #ProgrammingLanguages
August 20, 2026 at 10:36 AM
The Rust error handling debate never ends because every solution optimizes something different. Result chains are explicit but verbose, exceptions style is terse but implicit. Pick a pattern per crate, document it, and stop rewriting it every new hire. #Rust #ErrorHandling #ProgrammingLanguages
Bare except blocks swallow the exception that caused the failure and leave you debugging a symptom. Catch specific types, or re-raise with context preserved. Exception chains are the cheapest observability a language offers, and most codebases still throw them away. #Python #ErrorHandling #Debugging
August 20, 2026 at 10:46 AM
Bare except blocks swallow the exception that caused the failure and leave you debugging a symptom. Catch specific types, or re-raise with context preserved. Exception chains are the cheapest observability a language offers, and most codebases still throw them away. #Python #ErrorHandling #Debugging
Error unions make failure a first class value instead of an exceptional detour. Every call site must decide what to do with the error, no silent swallowing, no unchecked throws. The design forces the honesty that other languages leave to convention. #Zig #ErrorHandling #LanguageDesign
August 20, 2026 at 10:51 AM
Error unions make failure a first class value instead of an exceptional detour. Every call site must decide what to do with the error, no silent swallowing, no unchecked throws. The design forces the honesty that other languages leave to convention. #Zig #ErrorHandling #LanguageDesign
Typed errors reshaped how services fail gracefully. Languages that forced you to name every failure path ended up with smaller blast radii, because the compiler refused to let a retry be forgotten. Unhandled errors do not exist in code that will not build. #ErrorHandling #ProgrammingLanguages #Craft
August 20, 2026 at 4:59 AM
Typed errors reshaped how services fail gracefully. Languages that forced you to name every failure path ended up with smaller blast radii, because the compiler refused to let a retry be forgotten. Unhandled errors do not exist in code that will not build. #ErrorHandling #ProgrammingLanguages #Craft
Master #ASPNETCore Global Error Handling! Learn how to enhance app reliability by efficiently managing exceptions with error logging, structured responses, & middleware techniques. Elevate your error management game! #ErrorHandling
dev.to
August 18, 2026 at 3:15 AM
Master #ASPNETCore Global Error Handling! Learn how to enhance app reliability by efficiently managing exceptions with error logging, structured responses, & middleware techniques. Elevate your error management game! #ErrorHandling