@workos/quickstudy 0.6.0 → 0.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@workos/quickstudy",
-  "version": "0.6.0",
+  "version": "0.6.1",
   "description": "An open-source, company-agnostic eval harness for measuring whether coding agents can complete real integration tasks, across an agent x feature x framework x surface matrix.",
   "license": "MIT",
   "type": "module",

package/src/build-info.generated.ts

@@ -9,7 +9,7 @@ export const EMBEDDED_BUILD_INFO: {
   // (the `x-release-please-version` marker anchors the replacement). It is
   // restored as-is after a binary build (scripts/build-binary.ts), so the
   // committed source `--version` stays in lockstep with package.json.
-  version: "0.6.0", // x-release-please-version
+  version: "0.6.1", // x-release-please-version
   revision: null,
   dirty: null,
   sourceHash: null,

package/src/isolation/image-contexts.generated.ts

@@ -534,13 +534,28 @@ function dialUpstream(client: Socket, host: string, port: number, ready: (upstre
   });
 }
 
-/** Bidirectional tunnel wiring shared by CONNECT and plain forwards. */
+/**
+ * Bidirectional tunnel wiring shared by CONNECT and plain forwards.
+ *
+ * \`pipe()\` already ends the destination once the source ends — after the
+ * buffered bytes have flushed. Destroying the client on the upstream's
+ * \`close\` threw that buffer away: an upstream that closes right after a
+ * large response (a registry tarball) left the client with a truncated body
+ * and an ECONNRESET, so \`npm install\` through the proxy failed at random.
+ * So the upstream's close only ENDS the client (flush, then FIN). The other
+ * direction stays a destroy: a client that is gone will never read what the
+ * upstream still has to say, and a merely ended upstream would sit paused
+ * and half-open until the origin gave up.
+ */
 function pipeBoth(client: Socket, upstream: Socket): void {
   client.pipe(upstream);
   upstream.pipe(client);
-  client.on("close", () => upstream.destroy());
-  upstream.on("close", () => client.destroy());
   client.on("error", () => upstream.destroy());
+  upstream.on("error", () => client.destroy());
+  client.on("close", () => upstream.destroy());
+  upstream.on("close", () => {
+    if (!client.writableEnded) client.end();
+  });
 }
 
 /** CONNECT host:port — the HTTPS path. The tunnel is opaque to the proxy. */

package/src/isolation/proxy/server.ts

@@ -252,13 +252,28 @@ function dialUpstream(client: Socket, host: string, port: number, ready: (upstre
   });
 }
 
-/** Bidirectional tunnel wiring shared by CONNECT and plain forwards. */
+/**
+ * Bidirectional tunnel wiring shared by CONNECT and plain forwards.
+ *
+ * `pipe()` already ends the destination once the source ends — after the
+ * buffered bytes have flushed. Destroying the client on the upstream's
+ * `close` threw that buffer away: an upstream that closes right after a
+ * large response (a registry tarball) left the client with a truncated body
+ * and an ECONNRESET, so `npm install` through the proxy failed at random.
+ * So the upstream's close only ENDS the client (flush, then FIN). The other
+ * direction stays a destroy: a client that is gone will never read what the
+ * upstream still has to say, and a merely ended upstream would sit paused
+ * and half-open until the origin gave up.
+ */
 function pipeBoth(client: Socket, upstream: Socket): void {
   client.pipe(upstream);
   upstream.pipe(client);
-  client.on("close", () => upstream.destroy());
-  upstream.on("close", () => client.destroy());
   client.on("error", () => upstream.destroy());
+  upstream.on("error", () => client.destroy());
+  client.on("close", () => upstream.destroy());
+  upstream.on("close", () => {
+    if (!client.writableEnded) client.end();
+  });
 }
 
 /** CONNECT host:port — the HTTPS path. The tunnel is opaque to the proxy. */