Tag
This article presents techniques and a library for deferring error handling in Rust during development, allowing developers to temporarily downgrade errors to warnings to maintain productivity without sacrificing correctness.
The article contrasts Python and Rye scripts for downloading a PDF, highlighting how initial elegant code makes many assumptions about success. It then demonstrates adding validation, which reduces readability but improves robustness.
This article addresses the common Rust error when using a function that returns a Result within a map closure, and provides multiple solutions: collecting results, using a loop, filter_map, and try_fold.
A practical technique for improving structured output generation from LLMs by feeding validation errors back into retry prompts, allowing the model to self-correct rather than blindly retrying. The method involves describing the error in model-friendly terms and providing the previous output for editing.
Explores how AI agents should handle failures when third-party services go down during a workflow, highlighting the need for robust error handling in autonomous systems.
This article delves into the differences between C in the Linux kernel and ordinary userspace C, covering core techniques such as resource management, error handling, concurrency, logging, static analysis, and extensively using GNU C extensions and kernel-specific patterns.
A blog post discussing how excessive nil pointer checks in Go can indicate unclear code and poor error handling practices, advocating for early failure and explicit modeling of unavailable dependencies.
The author contrasts polished AI agent demos with the reality of production systems, noting that most agent code is for error handling and guardrails rather than the core intelligence.
A developer recounts how their automated pipeline silently skipped failed API calls due to rate limiting, producing seemingly successful runs with empty data. They discuss the trade-off between retrying and hard-failing, and ask the community for best practices in agent error handling.
A critique of poorly built automation systems created by so-called experts who ignore error handling, documentation, and governance, leaving clients with fragile workflows that fail in production.
A developer shares a lesson learned about capping tool retries per session rather than per call to prevent runaway costs from flaky endpoints, recommending a per-session retry budget that fails loud when exhausted.
The article presents a framework for interface design where every interface has two channels (in-band and out-of-band) for concern signaling, arguing that good design forces users to confront important concerns rather than allowing them to ignore them.
Introducing the Auxiliary Models feature in Hermes Agent, which allows independent configuration of models for each auxiliary task. It also includes a fallback mechanism that automatically switches to backup models. Support for the Hermes Desktop client is also mentioned.
This article explains how to add fault tolerance to LangGraph agents using RetryPolicy, TimeoutPolicy, and error handlers, covering retries with backoff, timeouts, and compensation logic for production reliability.
The builders of a multi-agent system added a dead man's switch that alerts a human when all four outbound communication channels are blocked simultaneously, preventing silent failures. The fix includes a dedup guard to avoid repeated alerts.
We released Trustabl Agent Analyzer, an open-source tool that scans AI agent repositories to find missing validation, retries, and error handling, generating a privacy-preserving local report.
A discussion about dealing with AI hallucination errors in business automations, focusing on damage control and practical mitigation strategies.
A blog post advocating for custom error types in Rust applications, explaining how to create a unified AppError enum using map_err and From traits to streamline error handling across different subsystems.
Kan-Ru Chen introduces `scoped-error`, a new Rust crate that aims to improve error handling ergonomics by scoping context attachment to the module level, addressing issues with existing crates like anyhow and thiserror.
The article criticizes C standard library functions for parsing integers (atol, strtol, strtoul, sscanf), explaining why most are broken and only strtol can be used correctly with careful error handling.