sliccy 6.112.4 → 6.112.5

package/dist/node-server/http-keepalive.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Keep-alive tuning for the local bridge HTTP server.
+ *
+ * Node's default `keepAliveTimeout` is 5 s, which Express advertises verbatim
+ * (`Keep-Alive: timeout=5`). That is far below Chrome's idle-socket timeout, so
+ * during a bursty fan-out — an in-browser `git status` walking a repo over
+ * `/api/hostfs` issues thousands of small requests in waves — the server closes
+ * a pooled socket in the same instant the browser writes the next request onto
+ * it. The browser cannot tell that apart from a dead server and rejects the
+ * `fetch()` with `TypeError: Failed to fetch`, which used to abort the whole
+ * git command (issue #2720).
+ *
+ * Holding idle sockets open for two minutes makes that race vanishingly rare on
+ * a loopback bridge that only ever serves this machine's browser. Sockets are
+ * still reaped, just on a scale the client's own pooling never reaches during a
+ * burst. `headersTimeout` must stay above `keepAliveTimeout`, otherwise Node
+ * aborts a connection it is still willing to keep.
+ */
+import { type Server as HttpServer, type RequestListener } from 'http';
+/** Idle keep-alive socket lifetime (ms). Advertised as `Keep-Alive: timeout=120`. */
+export declare const BRIDGE_KEEP_ALIVE_TIMEOUT_MS = 120000;
+/** Header-completion budget (ms). Must exceed `BRIDGE_KEEP_ALIVE_TIMEOUT_MS`. */
+export declare const BRIDGE_HEADERS_TIMEOUT_MS = 130000;
+/**
+ * Apply the bridge keep-alive settings to an HTTP server. Call before
+ * `listen()` — Node reads both values per connection, but a server that has
+ * already accepted sockets would keep the old budget for them.
+ */
+export declare function applyBridgeKeepAlive(server: HttpServer): void;
+/**
+ * Create the bridge's HTTP server with the keep-alive budget already applied,
+ * so no caller can construct one that still advertises `timeout=5`.
+ */
+export declare function createBridgeServer(requestListener: RequestListener): HttpServer;

package/dist/node-server/http-keepalive.js

@@ -0,0 +1,41 @@
+/**
+ * Keep-alive tuning for the local bridge HTTP server.
+ *
+ * Node's default `keepAliveTimeout` is 5 s, which Express advertises verbatim
+ * (`Keep-Alive: timeout=5`). That is far below Chrome's idle-socket timeout, so
+ * during a bursty fan-out — an in-browser `git status` walking a repo over
+ * `/api/hostfs` issues thousands of small requests in waves — the server closes
+ * a pooled socket in the same instant the browser writes the next request onto
+ * it. The browser cannot tell that apart from a dead server and rejects the
+ * `fetch()` with `TypeError: Failed to fetch`, which used to abort the whole
+ * git command (issue #2720).
+ *
+ * Holding idle sockets open for two minutes makes that race vanishingly rare on
+ * a loopback bridge that only ever serves this machine's browser. Sockets are
+ * still reaped, just on a scale the client's own pooling never reaches during a
+ * burst. `headersTimeout` must stay above `keepAliveTimeout`, otherwise Node
+ * aborts a connection it is still willing to keep.
+ */
+import { createServer } from 'http';
+/** Idle keep-alive socket lifetime (ms). Advertised as `Keep-Alive: timeout=120`. */
+export const BRIDGE_KEEP_ALIVE_TIMEOUT_MS = 120_000;
+/** Header-completion budget (ms). Must exceed `BRIDGE_KEEP_ALIVE_TIMEOUT_MS`. */
+export const BRIDGE_HEADERS_TIMEOUT_MS = 130_000;
+/**
+ * Apply the bridge keep-alive settings to an HTTP server. Call before
+ * `listen()` — Node reads both values per connection, but a server that has
+ * already accepted sockets would keep the old budget for them.
+ */
+export function applyBridgeKeepAlive(server) {
+    server.keepAliveTimeout = BRIDGE_KEEP_ALIVE_TIMEOUT_MS;
+    server.headersTimeout = BRIDGE_HEADERS_TIMEOUT_MS;
+}
+/**
+ * Create the bridge's HTTP server with the keep-alive budget already applied,
+ * so no caller can construct one that still advertises `timeout=5`.
+ */
+export function createBridgeServer(requestListener) {
+    const server = createServer(requestListener);
+    applyBridgeKeepAlive(server);
+    return server;
+}

package/dist/node-server/index.js

@@ -5,7 +5,6 @@ import { SLICC_HOSTED_ORIGIN } from './_shared/index.js';
 import { spawn } from 'child_process';
 import express from 'express';
 import { existsSync, readFileSync } from 'fs';
-import { createServer } from 'http';
 import { createServer as createNetServer } from 'net';
 import { homedir } from 'os';
 import { basename, dirname, join, resolve } from 'path';
@@ -32,6 +31,7 @@ import { shouldParseGlobalJson } from './fetch-proxy-headers.js';
 import { FileLogger } from './file-logger.js';
 import { registerHostedBootstrapEndpoint } from './hosted-bootstrap.js';
 import { registerHostFsRoutes, resolveHostMountRoots } from './hostfs.js';
+import { createBridgeServer } from './http-keepalive.js';
 import { runInstallCli } from './install-cli.js';
 import { resolveCliBrowserLaunchUrl } from './launch-url.js';
 import { createHttpCdp, registerLeaderRestartEndpoint } from './leader-restart.js';
@@ -1160,7 +1160,7 @@ async function main() {
     // surface. Chrome opens the sliccy.ai-hosted leader which talks to /cdp +
     // /api cross-origin. Create the HTTP server so we can attach the /cdp WS
     // upgrade handler to it.
-    const server = createServer(app);
+    const server = createBridgeServer(app);
     // 4. CDP WebSocket proxy at /cdp — noServer mode so we own the upgrade
     //    handler routing for /cdp and /licks-ws.
     const wss = createCdpWebSocketServer(state.bridgeToken);