@sayknow-cli/utils 0.5.1 → 0.5.4

package/package.json

@@ -1,7 +1,7 @@
 {
 	"type": "module",
 	"name": "@sayknow-cli/utils",
-	"version": "0.5.1",
+	"version": "0.5.4",
 	"description": "Shared utilities for pi packages",
 	"homepage": "https://sayknow-cli.com",
 	"author": "jaybeyond",
@@ -31,7 +31,7 @@
 		"fmt": "biome format --write ."
 	},
 	"dependencies": {
-		"@sayknow-cli/natives": "0.5.1",
+		"@sayknow-cli/natives": "0.5.4",
 		"beautiful-mermaid": "^1.1.3",
 		"handlebars": "^4.7.9",
 		"winston": "^3.19.0",

package/src/postmortem.ts

@@ -335,12 +335,25 @@ async function exitQuietlyForAttributableStdoutEpipe(reason: Reason): Promise<vo
 	if (process.exitCode === BROKEN_PIPE_EXIT_CODE) process.exit(BROKEN_PIPE_EXIT_CODE);
 }
 
+/**
+ * A benign shutdown write error means the sink is already dying, so routing a
+ * diagnostic through the logger can hit that same sink and raise the next
+ * identical fatal. Latching the note to one attempt per process bounds that:
+ * without it, a stdout EPIPE during cleanup drives an unbounded
+ * fatal -> log -> fatal loop that pins a core and grows the heap without limit
+ * instead of letting the process exit.
+ */
+let benignShutdownIoErrorNoted = false;
+
 async function handleFatalError(label: string, reason: unknown, cleanupReason: Reason): Promise<void> {
 	if (cleanupStage !== "idle" && isBenignIoWriteError(reason)) {
-		logger.debug("Ignoring benign terminal I/O write error during shutdown", {
-			code: (reason as { code?: unknown }).code,
-			syscall: (reason as { syscall?: unknown }).syscall,
-		});
+		if (!benignShutdownIoErrorNoted) {
+			benignShutdownIoErrorNoted = true;
+			logger.debug("Ignoring benign terminal I/O write error during shutdown", {
+				code: (reason as { code?: unknown }).code,
+				syscall: (reason as { syscall?: unknown }).syscall,
+			});
+		}
 		return;
 	}
 	if (stdoutEpipeClassifier.isAttributableProcessStdoutEpipe(reason)) {