From 4b3c5ed9475439b3b70ca66b8d0a8f4f639b5456 Mon Sep 17 00:00:00 2001
From: Karl Seguin <k@openmymind.io>
Date: Sun, 23 Aug 2026 13:37:08 +0800
Subject: [PATCH] chore: Silence the sporadic WriteFailed HTTP Error from the
 test server

No clue why this happens, but if the error mattered, a test would fail. A lot
of tests can be "harsh" on the server (e.g. a frame that navigates its parent
away while some resource load), so a WriteFailed error isn't exactly surprising
---
 src/TestHTTPServer.zig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/TestHTTPServer.zig b/src/TestHTTPServer.zig
index 574fb125a..877ee82b5 100644
--- a/src/TestHTTPServer.zig
+++ b/src/TestHTTPServer.zig
@@ -98,7 +98,7 @@ fn handleConnection(self: *TestHTTPServer, conn: std.Io.net.Stream) !void {
 
         self.handler(&req) catch |err| {
             switch (err) {
-                error.BrokenPipe => {},
+                error.BrokenPipe, error.WriteFailed => {},
                 else => {
                     std.debug.print("test http error '{s}': {}\n", .{ req.head.target, err });
                     req.respond("server error", .{ .status = .internal_server_error }) catch {};