Rust gains dedicated ErrorKind::TooManyOpenFiles variant for I/O error handling

·1 views

A new variant, TooManyOpenFiles, has been added to Rust's io::ErrorKind enum via PR #158326, giving developers a clean, platform-agnostic way to handle file descriptor exhaustion errors. Previously, both the per-process EMFILE and system-wide ENFILE errno codes were decoded into the generic Uncategorized variant, forcing developers to inspect raw OS error codes directly. The change maps the relevant Unix, WASI, and Windows error codes to the new variant, enabling straightforward pattern matching on error kind alone. The variant is currently unstable and must be enabled with the feature flag io_error_too_many_open_files. This marks the contributor's second merged change to Rust's standard library I/O layer, continuing a focus on improving low-level reliability.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How a Chinese Gym Runs 9 AI Agents on a Budget Server With No GPU

A fitness gym in China is running nine specialized AI agents on a bare-metal Ubuntu server with just 2 CPU cores and 3.6GB of RAM, with no GPU or cloud infrastructure. The agents handle tasks ranging from member fitness report interpretation and coach scheduling to investor relations, brand content, and security auditing. Heavy AI processing is offloaded entirely to the DeepSeek API, meaning the local server only manages orchestration, sessions, and file storage. Each agent is defined by three markdown files encoding its identity, mission, and operational rules, which serve as both runtime configuration and human-readable documentation. The project demonstrates that production-grade multi-agent AI systems can be built on minimal hardware when paired with a reliable external LLM API and a well-structured orchestration layer.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How a Three-Person Software Firm Uses Lean Inception and Shared Toolkits to Stay Efficient

A software engineering postgraduate student at PUC-RJ shares workflow lessons learned while running Devtype, a small three-person development company. The team adopted Jira for project management and began using Excalidraw for system architecture diagrams, but found that rushing into design without first gathering requirements was counterproductive. The author now advocates for lean inception sessions — structured conversations to define customer needs, tasks, and deadlines — before any technical diagramming begins. Reaching a minimum viable product (MVP) quickly is emphasized as the key milestone that turns ideas into reality. The team also built reusable backend toolkits covering database connections, AWS integration, authentication, and more, which improved consistency and maintainability across projects.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How AI Agents Are Forcing a Rethink of Ecommerce Platform Architecture

AI agents are reshaping the assumptions behind ecommerce software, exposing gaps in platforms originally designed for human users. Unlike humans, agents cannot reliably interpret mixed or ambiguous product pages and require explicit, machine-readable representations of eligibility, policies, and permitted actions. A technical article series has outlined a new architectural model for agent-ready commerce, centered on facts, authority, state transitions, and audit trails rather than traditional page-driven flows. The proposed approach goes beyond exposing product feeds or API endpoints, requiring platforms to surface the conditions under which commercial actions are valid. A key concept introduced is "commercial truth" — structured metadata that conveys data freshness, policy coverage, and agent visibility separately from raw product information.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Kubexer tool automates Kubernetes scoped kubeconfig creation to enforce least-privilege access

Creating a scoped kubeconfig for Kubernetes — which limits a user or bot to specific namespaces and permissions — typically requires around 15 manual steps spanning multiple object types and commands. The process involves creating a ServiceAccount, Role, RoleBinding, extracting a token, handling the cluster CA, and assembling the final file, leaving many opportunities for error. Common pitfalls include over-broad permissions, token expiry issues, leaked temporary files, and no audit trail of who created which credentials. This friction often leads teams to share over-privileged admin credentials instead, increasing security risk. A developer has built Kubexer, a desktop IDE for Kubernetes, which collapses the entire workflow into a guided interface where users simply define the namespace, resources, verbs, and token lifetime.

0 comments Read more at DEV Community