@rotorsoft/act 1.33.19 → 1.33.20

package/dist/index.js

@@ -2343,15 +2343,14 @@ async function run_drain_cycle(deps, cycle) {
       return handle({ ...lease, at }, payloads);
     })
   );
-  const blocked = await ops.block(
-    handled.filter(({ block: block2 }) => block2).map(({ lease, error }) => ({ ...lease, error }))
-  );
+  const to_block = handled.filter(({ block: block2 }) => block2).map(({ lease, error }) => ({ ...lease, error }));
+  const blocked = to_block.length ? await ops.block(to_block) : [];
   if (blocked.length) deps.on_blocked(blocked);
   const submitted = handled.flatMap((h, i) => {
     const advance = h.handled > 0 ? h.acked_at : leased[i].at;
     return h.defer !== void 0 ? { ...h.lease, at: advance, due: h.defer, retry: -1 } : h.next_attempt_at !== void 0 ? { ...h.lease, at: advance, due: h.next_attempt_at } : h.handled > 0 || !h.error ? { ...h.lease, at: h.acked_at } : [];
   });
-  const acked = await ops.ack(submitted);
+  const acked = submitted.length ? await ops.ack(submitted) : [];
   const expected = submitted.filter((l) => l.due === void 0).length;
   if (acked.length < expected)
     log().warn(
@@ -2854,9 +2853,8 @@ var SettleLoop = class {
    * `debounceMs` brings it forward), and a call during a running cycle
    * queues one more pass after it. Callers pass options, which the next
    * pass uses; internal wake-ups pass none, so they never discard a
-   * caller's. The cycle runs correlate→drain in a
-   * loop until a pass makes no progress (it read no events and leased no
-   * streams) or `maxPasses` is reached, then emits the
+   * caller's. The cycle runs correlate→drain passes until one makes no
+   * progress (see {@link SettleOptions.maxPasses}), then emits the
    * `"settled"` lifecycle event via {@link SettleDeps.on_settled}.
    */
   schedule(options) {
@@ -3906,8 +3904,8 @@ var Act = class {
    * `unblock()`, `restore()`) schedules this on its own unless the app
    * sets `autoSettle: false`. Call it at startup, to run what was pending
    * before a restart, or with options for the next pass; the scheduling
-   * rule is in the event-sourcing docs (§ settle). Runs correlate→drain in a loop until a pass makes no
-   * progress — it read no events and leased no streams —
+   * rule is in the event-sourcing docs (§ settle). Runs correlate→drain
+   * passes until one makes no progress (see {@link SettleOptions.maxPasses}),
    * then emits the `"settled"` lifecycle event, so one call fully catches
    * up paginated streams without forcing callers to loop.
    *