@camstack/server 1.2.262 → 1.2.263

package/dist/main.js

@@ -404,6 +404,22 @@ async function bootstrap() {
             heapWatchLogger.warn(line);
         },
     });
+    // ...and the OTHER thing the heartbeat cannot see. `[mem]` is a 5-minute
+    // timer: it fired at dt = 300020 / 300066 / 299991 ms straight through the
+    // 2026-09-09 analytics silences, which proves nothing about a 10-second
+    // freeze. Every runner's UDS request waits on THIS loop, so a hub-main stall
+    // is delivered to every addon as "you are slow" — the exact confusion
+    // `pipeline-analytics`' frame-lag line exists to break, and this is the half
+    // that says whether hub-main was the one holding the events. Same monitor
+    // `detection-pipeline`, `recorder` and `pipeline-analytics` arm.
+    //
+    // Armed HERE and not at the top of `bootstrap()`, for the reason the heap
+    // sink is deferred: before `loggingService` exists the lines could only
+    // reach `console.log`, which is not a log destination. Never stopped: the
+    // interval is `unref`ed, so it cannot hold the process open, and hub-main's
+    // shutdown is process exit.
+    const stallLogger = loggingService.createLogger('event-loop');
+    (0, system_1.startEventLoopStallMonitor)(stallLogger);
     const addonRouteRegistry = new system_1.AddonRouteRegistry();
     const dataPlaneRegistry = new system_1.DataPlaneRegistry();
     // Use Fastify-managed notification/toast wrappers (globally provided by NotificationModule)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@camstack/server",
-  "version": "1.2.262",
+  "version": "1.2.263",
   "private": false,
   "files": [
     "dist",