@torrent-tv/proxy 2.9.38 → 2.9.39

package/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 2.9.39
+
+- **Chore**: Log the stack (first frames) of WebTorrent `warning` events, not just the message. Field diagnosis: a playback froze mid-file with repeated `torrent-pool: … warning: Connection error: Cannot read properties of null (reading 'type')` (a WebTorrent µTP null-peer NPE, webtorrent#1932/#1940) while the swarm had seeders — peer connections were failing and the download starved. The old handler logged only the terse message, hiding which library path threw; the stack pinpoints it before we mitigate (next: prefer HTTP/DHT over the timing-out UDP trackers, then consider disabling µTP).
+
 ## 2.9.38
 
 - **New**: Adaptive bitrate for thin viewer links (OpenSpec change `adaptive-bitrate`). Field evidence (iPhone on cellular): uncapped complex scenes produced 4 s segments of ~18 Mbit/s against a 1–6 Mbit/s link — 45 s prebuffer and a draining buffer. Two parts. (a) Software encodes are now constrained-CRF: `-maxrate`/`-bufsize` per resolution rung (1080p→5000K, 720p→2800K, 480p→1400K, 360p→800K, 240p→400K nominal; ×1.3/×1.5 — webtor's production multipliers), so peaks stay bounded. (b) New data-channel route `POST /api/transcode-sessions/:id/net-report` accepts the browser's measured link throughput + buffered seconds; the realtime-budget loop gains a second downshift trigger — a FRESH report showing the usable link (×0.8 safety) sustainedly (15 s) below the observed produced bitrate while the viewer's buffer is low (<10 s) steps the encode one rung down via the existing machinery (shared 30 s cooldown, step cap, no upswitch). Log reason `viewer-link-bound` distinguishes it from CPU downshifts. Manual-quality sessions are exempt (no budget ladder); old clients that never report simply keep today's behaviour plus the caps.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@torrent-tv/proxy",
-  "version": "2.9.38",
+  "version": "2.9.39",
   "description": "Torrent proxy client that exposes webseed-like HTTP stream endpoint.",
   "license": "GPL-3.0-or-later",
   "publishConfig": {

package/services/torrent-pool.js

@@ -49,6 +49,24 @@ const DISK_CAP_SWEEP_INTERVAL_MS = 30_000;
  * asked to hold more than it can). Best-effort; falls back to the fixed max
  * when the filesystem cannot be stat'd.
  *
+ * Format a WebTorrent warning for logging: message plus a bounded stack.
+ * WebTorrent surfaces internal peer-connection failures (e.g. the µTP
+ * null-peer NPEs, webtorrent#1932/#1940) as non-fatal "warning" events
+ * carrying only a terse message; the stack pinpoints the exact library path,
+ * so we log the first few frames to diagnose which failure it is.
+ *
+ * @param {unknown} warning
+ * @returns {string}
+ */
+function formatWarning(warning) {
+  if (!(warning instanceof Error)) {
+    return String(warning);
+  }
+  const stack = typeof warning.stack === "string" ? warning.stack.split("\n").slice(0, 4).join(" | ") : "";
+  return stack || warning.message;
+}
+
+/**
  * @param {string} storePath
  * @returns {number}
  */
@@ -162,8 +180,7 @@ export class TorrentPool {
       logger.error(`WebTorrent client error: ${error.message}`);
     });
     this.client.on("warning", (warning) => {
-      const message = warning instanceof Error ? warning.message : String(warning);
-      logger.warn(`torrent-pool: client warning: ${message}`);
+      logger.warn(`torrent-pool: client warning: ${formatWarning(warning)}`);
     });
 
     this.#maxDiskBytes = Number.isFinite(maxDiskBytes) && maxDiskBytes >= 0
@@ -250,8 +267,7 @@ export class TorrentPool {
     );
 
     torrent.on("warning", (warning) => {
-      const message = warning instanceof Error ? warning.message : String(warning);
-      logger.warn(`torrent-pool: [${label}] warning: ${message}`);
+      logger.warn(`torrent-pool: [${label}] warning: ${formatWarning(warning)}`);
     });
 
     // bittorrent-tracker's Client emits "update" with each announce response.