kern-sandbox 0.1.12 → 0.1.13

package/README.md

@@ -2,7 +2,7 @@
 
 **[kern](https://github.com/getkern/kern)** is a fast, rootless sandbox and virtual resource
 runtime for any workload, including untrusted and AI-generated code: a real, kernel-enforced box
-that starts in **3.6 ms** from an OCI image, out of one **~1.8 MB** binary, with no daemon.
+that starts in **3.4 ms** from an OCI image, out of one **~1.8 MB** binary, with no daemon.
 **kern-sandbox**
 is its Node / TypeScript binding: run untrusted or agent-generated code in a fresh, isolated box, from Node.
 
@@ -177,7 +177,7 @@ can still WRITE an artifact to the workspace and `readFile` it if you prefer.
 **Warm kernel (kill the interpreter boot).** Each `runCode` starts a **fresh** interpreter, paying the
 CPython boot (~12 ms) every call. When you run many cells that share state (a REPL, a notebook, an
 agent's tool loop), open a `kernel()`: ONE warm interpreter in a long-lived box, fed cells over a pipe.
-In-memory state persists across cells and the per-cell cost drops from ~16 ms to **sub-millisecond**
+In-memory state persists across cells and the per-cell cost drops from ~14 ms to **sub-millisecond**
 (~300x). Same rich `results` capture as `runCode`.
 
 ```js

package/index.js

@@ -36,7 +36,7 @@ const crypto = require("crypto");
 const zlib = require("zlib");
 const { spawn, spawnSync } = require("child_process");
 
-const VERSION = "0.1.12";
+const VERSION = "0.1.13";
 
 const DEFAULT_IMAGE = "python:3.12-slim";
 const WORKSPACE = "/workspace"; // where the persistent workspace is mounted inside every box
@@ -968,19 +968,16 @@ class Sandbox {
       const err = cappedCollector(child.stderr, this.maxOutputBytes, cbErr);
       let timedOut = false;
       let settled = false;
-
-      const timer = setTimeout(() => {
-        timedOut = true;
-        this._teardown(child, name, childEnv);
-      }, timeoutS * 1000);
-
-      // Hard safety net: a CPU-bound box can survive our signals until kern's backstop reaps it; never
-      // hang the caller. If close hasn't fired a few seconds after our teardown, resolve anyway.
+      // Both timers are armed further down, once `finish` exists. They are declared here, as `let`,
+      // so the closures that clear them can never reference a binding in its temporal dead zone
+      // whatever the callback ordering turns out to be.
+      let timer = null;
       let hardTimer = null;
+
       const finish = (code, signal) => {
         if (settled) return;
         settled = true;
-        clearTimeout(timer);
+        if (timer) clearTimeout(timer);
         if (hardTimer) clearTimeout(hardTimer);
         // kern has read the file by the time it exits; leaving it behind would accrete one per call
         // in a persistent `workspace`.
@@ -1008,20 +1005,22 @@ class Sandbox {
       child.on("close", (code, signal) => {
         finish(code, signal);
       });
-      // arm the hard net only once we've decided to kill (teardown sets timedOut)
+      // Hard safety net: a CPU-bound box can survive our signals until kern's backstop reaps it;
+      // never hang the caller. If close hasn't fired a few seconds after our teardown, resolve anyway.
       const armHardNet = () => {
         if (hardTimer) return;
         hardTimer = setTimeout(() => finish(EXIT_SIGKILL, "SIGKILL"), 10000);
       };
-      // re-check shortly after the deadline in case teardown fired
-      const watch = setInterval(() => {
-        if (settled) {
-          clearInterval(watch);
-        } else if (timedOut) {
-          clearInterval(watch);
-          armHardNet();
-        }
-      }, 250);
+
+      timer = setTimeout(() => {
+        timedOut = true;
+        this._teardown(child, name, childEnv);
+        // Armed HERE, at the one place that decides to kill. It used to be noticed instead by a
+        // 250 ms setInterval that `finish` never cleared, so after every call that interval kept the
+        // event loop alive until its own next tick: measured 224 to 232 ms of dead time between a
+        // call resolving and the process being able to exit, against 19 to 27 ms of real work.
+        armHardNet();
+      }, timeoutS * 1000);
     });
   }
 
@@ -1726,7 +1725,24 @@ class Kernel {
       } catch {
         /* ignore */
       }
-      await new Promise((r) => setTimeout(r, 150));
+      // Wait for the exit EVENT, capped at 150 ms, rather than sleeping 150 ms unconditionally: that
+      // fixed sleep cost 152 ms on every close of a persistent kernel (measured) for a box that
+      // exits in a few. A child that is already gone has emitted `exit` and will not emit it again,
+      // so that case is tested directly instead of waited on.
+      if (child.exitCode === null && child.signalCode === null) {
+        await new Promise((resolve) => {
+          let t = null;
+          const onExit = () => {
+            if (t !== null) clearTimeout(t);
+            resolve();
+          };
+          t = setTimeout(() => {
+            child.removeListener("exit", onExit);
+            resolve();
+          }, 150);
+          child.once("exit", onExit);
+        });
+      }
       this._kill();
     } else {
       this._kill();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kern-sandbox",
-  "version": "0.1.12",
+  "version": "0.1.13",
   "description": "kern is a fast, rootless sandbox and virtual resource runtime for any workload, including untrusted and AI-generated code; kern-sandbox is its Node/TypeScript binding. Run untrusted or agent-generated code (Python/JS/Bash) in a real, kernel-enforced box in single-digit milliseconds, with no cloud, no account and no VM.",
   "keywords": [
     "sandbox",