@oneuptime/common 11.3.22 → 11.3.23

package/Server/Utils/EventLoop.ts

@@ -0,0 +1,28 @@
+export default class EventLoop {
+  /**
+   * Yields control back to the Node.js event loop, resuming on a later
+   * "check" phase tick.
+   *
+   * Use this to break up CPU-bound synchronous work — e.g. transforming
+   * tens of thousands of OTLP datapoints / spans / log records inside a
+   * single ingest job — so the process can service pending I/O between
+   * chunks. Most importantly, this lets the Kubernetes liveness and
+   * readiness probe handlers (/status/live, /status/ready) run. Without a
+   * periodic yield a large batch pins the single-threaded event loop for
+   * seconds at a time, the probe HTTP handler never gets scheduled, the
+   * kubelet marks the probe as failed, and the pod is restarted.
+   *
+   * IMPORTANT: this is implemented with setImmediate, NOT
+   * `await Promise.resolve()`. Awaiting a resolved promise only drains the
+   * microtask queue; the event loop never advances to its poll phase, so
+   * queued I/O (including probe requests) stays starved no matter how often
+   * you await. setImmediate schedules a macrotask in the check phase, which
+   * runs only after the poll phase has had a chance to process I/O — so a
+   * loop that periodically awaits this genuinely unblocks the event loop.
+   */
+  public static async yieldToEventLoop(): Promise<void> {
+    return new Promise<void>((resolve: () => void) => {
+      setImmediate(resolve);
+    });
+  }
+}

package/build/dist/Server/Utils/EventLoop.js

@@ -0,0 +1,29 @@
+export default class EventLoop {
+    /**
+     * Yields control back to the Node.js event loop, resuming on a later
+     * "check" phase tick.
+     *
+     * Use this to break up CPU-bound synchronous work — e.g. transforming
+     * tens of thousands of OTLP datapoints / spans / log records inside a
+     * single ingest job — so the process can service pending I/O between
+     * chunks. Most importantly, this lets the Kubernetes liveness and
+     * readiness probe handlers (/status/live, /status/ready) run. Without a
+     * periodic yield a large batch pins the single-threaded event loop for
+     * seconds at a time, the probe HTTP handler never gets scheduled, the
+     * kubelet marks the probe as failed, and the pod is restarted.
+     *
+     * IMPORTANT: this is implemented with setImmediate, NOT
+     * `await Promise.resolve()`. Awaiting a resolved promise only drains the
+     * microtask queue; the event loop never advances to its poll phase, so
+     * queued I/O (including probe requests) stays starved no matter how often
+     * you await. setImmediate schedules a macrotask in the check phase, which
+     * runs only after the poll phase has had a chance to process I/O — so a
+     * loop that periodically awaits this genuinely unblocks the event loop.
+     */
+    static async yieldToEventLoop() {
+        return new Promise((resolve) => {
+            setImmediate(resolve);
+        });
+    }
+}
+//# sourceMappingURL=EventLoop.js.map

package/build/dist/Server/Utils/EventLoop.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"EventLoop.js","sourceRoot":"","sources":["../../../../Server/Utils/EventLoop.ts"],"names":[],"mappings":"AAAA,MAAM,CAAC,OAAO,OAAO,SAAS;IAC5B;;;;;;;;;;;;;;;;;;;;OAoBG;IACI,MAAM,CAAC,KAAK,CAAC,gBAAgB;QAClC,OAAO,IAAI,OAAO,CAAO,CAAC,OAAmB,EAAE,EAAE;YAC/C,YAAY,CAAC,OAAO,CAAC,CAAC;QACxB,CAAC,CAAC,CAAC;IACL,CAAC;CACF"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@oneuptime/common",
-  "version": "11.3.22",
+  "version": "11.3.23",
   "description": "",
   "repository": {
     "type": "git",