@volter/teams 0.2.50 → 0.2.52

package/board-owner.mjs

@@ -1,7 +1,8 @@
 // A home's board owner (`supercode workflow serve`, one per install: D152) answers every card verb on that home's boards
 // over one local socket. The CLI and the machine daemon's board door hold nothing: each sends the verb here and renders
 // the answer. The socket is the home's own (`<home>/board.sock`, beside the owner's lock `<home>/board.lock`), by the
-// home's real path, so every process naming the home reaches the one owner whatever its environment.
+// home's real path, so every process naming the home reaches the one owner whatever its environment. On Windows, where
+// Node listens only on named pipes, it is the pipe named by that path.
 //
 //   request:  one JSON line  { v: 1, argv | tool, board, caller, session, facts, cwd, stdin }
 //               argv     the verb and its arguments, without --root or --board
@@ -19,6 +20,7 @@
 import { existsSync, realpathSync } from 'node:fs';
 import { connect } from 'node:net';
 import { join, resolve } from 'node:path';
+import { shortSocketPath } from './home.mjs';
 
 /** A Unix socket's path is at most 104 bytes on macOS (108 on Linux), terminator included. */
 const SOCKET_PATH_MAX = 103;
@@ -30,6 +32,9 @@ export function boardHome(root) {
 
 /** The owner's socket for the home at `root`: the home's own, by its real path. */
 export function boardOwnerSocket(root) {
+  // Node on Windows listens only on named pipes (on a socket path it is refused, EACCES): there the owner's door is the
+  // pipe named by that path, as the machine daemon's is
+  if (process.platform === 'win32') return shortSocketPath(boardHome(root), 'board.sock');
   const path = join(boardHome(root), 'board.sock');
   if (Buffer.byteLength(path) > SOCKET_PATH_MAX) throw new Error(`the home's board socket ${path} is longer than a Unix socket path may be (${SOCKET_PATH_MAX} bytes); keep the home at a shorter path`);
   return path;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@volter/teams",
-  "version": "0.2.50",
+  "version": "0.2.52",
   "type": "module",
   "description": "Volter Teams, the neutral team plane: machine identity and daemon core, the local door and server link, admission from machine grants, product doors, and the Teams server's neutral routes (company RFC 0008).",
   "license": "MIT",

package/session-follow.mjs

@@ -2,6 +2,11 @@
 // the hosted viewer uses, exported so a workplace that draws the session itself (RH2's Conversation, supercode-ui in
 // its own tree) reads and labels it the same way. No imports: it runs as the viewer's own module and in a host's bundle.
 
+// A signal that aborts `ms` from now, for use inside AbortSignal.any(). Its timer holds its controller, so it fires
+// whatever the garbage collector does. AbortSignal.timeout() inside AbortSignal.any() does not on Node 23.9: the timeout
+// signal is collected, the combined signal never aborts, and a request to a server that went quiet never ends.
+const timeoutSignal=ms=>{const controller=new AbortController(),timer=setTimeout(()=>controller.abort(new DOMException('The operation was aborted due to timeout','TimeoutError')),ms);timer.unref?.();return controller.signal;};
+
 /**
  * Follow one session: its snapshot read whole (`/messages?tail=`, a busy session's is over the follow stream's 1 MB
  * buffer), then its follow stream from that snapshot's cursor, each change meaning "read again". The stream ends when
@@ -25,7 +30,7 @@ export function followTeamSession({ origin, teamId, sessionId, token, tail = 300
       let snapshot;
       do {
         requested = false;
-        const response = await fetchImpl(`${base}/messages?tail=${tail}`, { headers: await headers(), signal: AbortSignal.any([controller.signal, AbortSignal.timeout(15000)]) });
+        const response = await fetchImpl(`${base}/messages?tail=${tail}`, { headers: await headers(), signal: AbortSignal.any([controller.signal, timeoutSignal(15000)]) });
         if (!response.ok) throw failure('read', response.status, `reading the session failed (${response.status})`);
         const body = await response.json();
         if (controller.signal.aborted) throw new DOMException('Session follow stopped', 'AbortError');