EPIPE on write might mean you're doing it wrong
Summary
A technical discussion about EPIPE errors on write, suggesting that encountering EPIPE often indicates a design issue in how the program handles broken pipes.
Similar Articles
Epoll vs. Io_uring in Linux
A technical comparison of epoll and io_uring in Linux, explaining their architectures and performance characteristics for asynchronous I/O.
Bad Epoll (CVE-2026-46242)
Bad Epoll (CVE-2026-46242) is a race-condition use-after-free vulnerability in the Linux kernel's epoll subsystem that allows unprivileged users to escalate to root on both Linux and Android devices. It was reported by Jaeyoung Chung and was missed by Anthropic's Mythos AI.
Pipes, Forks, and Zombies
This article from Harvard's CS 61 course covers Unix concepts of pipes, forks, and zombies, explaining how pipes automatically kill programs on closure and how to use pipes to implement blocking waits on child processes.
My pipeline ran "successfully" for a week. Turned out my agent had been silently skipping failed API calls the whole time.
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.
An unusually practical update for EYG
EYG programming language receives practical updates including documented text syntax, new filesystem effects in the CLI, and improved parser errors to facilitate shell scripting.