Tag
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.
This article from The Old New Thing explains the concept of making APIs 'inert'—do nothing in a way that avoids breaking existing apps—using examples like printing support on Xbox and retiring widget APIs.
The author describes a common user onboarding problem with MCP servers—users opening the endpoint in a browser and seeing a 401 error—and shares a simple hack: returning an HTML page that explains how to properly add the server to an LLM client, which drastically reduced support tickets.
The article highlights a lack of benchmarks for evaluating the reliability of agent harnesses, specifically focusing on how MCP implementations handle tool calls and errors compared to the models themselves.
A developer catalogued JSON output failures across 288 local model runs, finding common issues like markdown fences and trailing commas, and built outputguard, a Python library to repair invalid JSON with 15 strategies.
This article discusses Wix's initiative to improve thousands of error messages across its platform, defining characteristics of good versus bad error handling in UX design. It emphasizes clarity, empathy, and actionable solutions over technical jargon or blaming users.
This article explains how to build a Claude agent using Python, emphasizing the importance of handling tool failure cases effectively rather than just relying on happy-path scenarios.
The article discusses the complexities of implementing idempotency in APIs, arguing that handling edge cases like concurrent requests and content mismatches is harder than simple replay caching.
A blog post detailing a minimal pattern for adding error context in Zig using errdefer logging, comparing it to full diagnostics sinks and catch blocks, and discussing tradeoffs.
该文章介绍了在Zig中使用诊断工厂模式来管理错误报告，避免预先定义错误类型，而是提供一组构造函数来生成错误信息，并展示了在TigerBeetle项目中的实际应用。