@hotmeshio/hotmesh 0.0.10 → 0.0.11

package/services/pipe/functions/number.ts

@@ -70,81 +70,6 @@ class NumberHandler {
   round(input: number): number {
     return Math.round(input);
   }
-
-  add(...operands: (number | number[])[]): number {
-    // @ts-ignore
-    return operands.reduce((a: number, b: number | number[]) => {
-      if (Array.isArray(b)) {
-        return a + this.add(...b);
-      } else {
-        return a + b;
-      }
-    }, 0);
-  }
-
-  subtract(...operands: (number | number[])[]): number {
-    if (operands.length === 0) {
-      throw new Error('At least one operand is required.');
-    }
-    let flatOperands: number[] = [];
-    operands.forEach((op: number | number[]) => {
-      if (Array.isArray(op)) {
-        flatOperands = [...flatOperands, ...op];
-      } else {
-        flatOperands.push(op);
-      }
-    });
-    if (flatOperands.length === 0) {
-      throw new Error('At least one operand is required after flattening.');
-    }
-    const result = flatOperands.reduce((a: number, b: number, i: number) => {
-      return i === 0 ? a : a - b;
-    });
-    return result;
-  }
-  
-  
-  multiply(...operands: (number | number[])[]): number {
-    if (operands.length === 0) {
-      throw new Error('At least one operand is required.');
-    }
-  
-    // @ts-ignore
-    return operands.reduce((a: number, b: number | number[]) => {
-      if (Array.isArray(b)) {
-        return a * this.multiply(...b);
-      } else {
-        return a * b;
-      }
-    }, 1);
-  }
-  
-  divide(...operands: (number | number[])[]): number {
-    if (operands.length === 0) {
-      throw new Error('At least one operand is required.');
-    }
-    let flatOperands: number[] = [];
-    operands.forEach((op: number | number[]) => {
-      if (Array.isArray(op)) {
-        flatOperands = [...flatOperands, ...op];
-      } else {
-        flatOperands.push(op);
-      }
-    });
-    if (flatOperands.length === 0) {
-      throw new Error('At least one operand is required after flattening.');
-    }
-    const result = flatOperands.reduce((a: number, b: number, i: number) => {
-      if (b === 0) {
-        return NaN;
-      }
-      return i === 0 ? a : a / b;
-    });
-    if (isNaN(result)) {
-      return NaN;
-    }
-    return result;
-  }  
 }
 
 export { NumberHandler };

package/services/signaler/stream.ts

@@ -16,7 +16,7 @@ import {
   StreamStatus
 } from '../../types/stream';
 
-const MAX_RETRIES = 4; //max delay (10s using exponential backoff);
+const MAX_RETRIES = 3; //local retry; 10, 100, 1000ms
 const MAX_TIMEOUT_MS = 60000;
 const GRADUATED_INTERVAL_MS = 5000;
 const BLOCK_DURATION = 15000; //Set to `15` so SIGINT/SIGTERM can interrupt; set to `0` to BLOCK indefinitely
@@ -189,8 +189,11 @@ class StreamSignaler {
     const policy = policies?.[errorCode];
     const maxRetries = policy?.[0];
     const tryCount = Math.min(input.metadata.try || 0,  MAX_RETRIES);
-    if (maxRetries >= tryCount) {
-      return[true, Math.pow(10, tryCount)];
+    //only possible values for maxRetries are 1, 2, 3
+    //only possible values for tryCount are 0, 1, 2
+    if (maxRetries > tryCount) {
+      // 10ms, 100ms, or 1000ms delays between system retries
+      return[true, Math.pow(10, tryCount + 1)];
     }
     return [false, 0];
   }

package/types/durable.ts

@@ -9,7 +9,7 @@ type WorkflowOptions = {
   workflowSpan?: string;
 }
 
-type ActivityDataType = {
+type ActivityWorkflowDataType = {
   activityName: string;
   arguments: any[];
   workflowId: string;
@@ -41,7 +41,13 @@ type WorkerConfig = {
   connection: Connection;
   namespace?: string; //`appid` in the YAML (e.g, 'default')
   taskQueue: string; //`subscribes` in the YAML (e.g, 'hello-world')
-  workflow: Function //target function to run
+  workflow: Function; //target function to run
+  options?: WorkerOptions;
+}
+
+type WorkerOptions = {
+  maxSystemRetries?: number; //1-3 (10ms, 100ms, 1_000ms)
+  backoffExponent?: number; //2-10ish
 }
 
 type ContextType = {
@@ -67,7 +73,7 @@ type ActivityConfig = {
 
 export {
   ActivityConfig,
-  ActivityDataType,
+  ActivityWorkflowDataType,
   ClientConfig,
   ContextType,
   ConnectionConfig,
@@ -76,6 +82,7 @@ export {
   ProxyType,
   Registry,
   WorkerConfig,
+  WorkerOptions,
   WorkflowDataType,
   WorkflowOptions,
-};
+};

package/types/index.ts

@@ -26,6 +26,21 @@ export { CacheMode } from './cache';
 export {
   CollationFaultType,
   CollationStage } from './collator';
+export {
+    ActivityConfig,
+    ActivityWorkflowDataType,
+    ClientConfig,
+    ContextType,
+    ConnectionConfig,
+    Connection,
+    NativeConnection,
+    ProxyType,
+    Registry,
+    WorkerConfig,
+    WorkerOptions,
+    WorkflowDataType,
+    WorkflowOptions,
+  }from './durable'
 export {
   HookCondition,
   HookConditions,

package/build/services/dimension/index.d.ts

@@ -1,29 +0,0 @@
-import { HotMeshGraph } from '../../types/hotmesh';
-declare class DimensionService {
-    static targetLength: number;
-    /**
-     * entry point for compiler-type activities. This is called by the compiler
-     * to bind the sorted activity IDs to the trigger activity. These are then used
-     * at runtime by the activities to track job/activity status.
-     * @param graphs
-     */
-    static compile(graphs: HotMeshGraph[]): void;
-    /**
-     * All activities exist on a dimensional plane. Zero
-     * is the default and is implied if no dimension is
-     * present in the hash item key. EVERY value in the
-     * job ledger is dimensionalized even if the dimension
-     * is not present. The key, `AaA`, might not contain
-     * a dimensional index, but it is still implicitly
-     * dimensionalized as `AaA,0` (assuming a trigger).
-     * A value of `AxY,0,0,0,0,1,0,0` would reflect that
-     * an ancestor activity was dimensionalized beyond
-     * the default. The dimensional string must
-     * be included if not zero. There is likely a preceding
-     * sibling dimension, so it would not need to include
-     * the suffix, so these addresses are equivalent:
-     * `AxY,0,0,0,0,0,0,0` == `AxY` for said sibling.
-     */
-    static getSeed(index?: number): string;
-}
-export { DimensionService };

package/build/services/dimension/index.js

@@ -1,35 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.DimensionService = void 0;
-class DimensionService {
-    /**
-     * entry point for compiler-type activities. This is called by the compiler
-     * to bind the sorted activity IDs to the trigger activity. These are then used
-     * at runtime by the activities to track job/activity status.
-     * @param graphs
-     */
-    static compile(graphs) {
-    }
-    /**
-     * All activities exist on a dimensional plane. Zero
-     * is the default and is implied if no dimension is
-     * present in the hash item key. EVERY value in the
-     * job ledger is dimensionalized even if the dimension
-     * is not present. The key, `AaA`, might not contain
-     * a dimensional index, but it is still implicitly
-     * dimensionalized as `AaA,0` (assuming a trigger).
-     * A value of `AxY,0,0,0,0,1,0,0` would reflect that
-     * an ancestor activity was dimensionalized beyond
-     * the default. The dimensional string must
-     * be included if not zero. There is likely a preceding
-     * sibling dimension, so it would not need to include
-     * the suffix, so these addresses are equivalent:
-     * `AxY,0,0,0,0,0,0,0` == `AxY` for said sibling.
-     */
-    static getSeed(index = 0) {
-        return `,${index}`;
-    }
-}
-exports.DimensionService = DimensionService;
-//max int digit count that supports `hincrby`
-DimensionService.targetLength = 15;

package/services/dimension/README.md

@@ -1,73 +0,0 @@
-# Optimizing Cycle Management Through Shared Collation State
-Activity state is managed using a 15-digit integer. For all non-trigger activities, this value is initialized by the parent activity/preceding in the DAG. (Triggers are initialized in a 'completed' state, since their execution only reflects the  completion of the Leg 2 Duplex.)
-
->Presetting the value for subsequent generations is critical to establishing return receipt checks, so that the system can guarantee durability and idempotency in the result of system failure during handoff.
-
-The first three digits of the 15-digit integer track and convey the activity lifecycle status. Supporting 3 states using any 3 integers is the only critical requirement for the chosen integers. As long as the backend system supports decrement and increment commands that return the modified integer value, the system can durably track state using the strategy described here.  In the reference implementation, the digit `9` is “pending” and `8` is “complete”. Additional digits can be employed to convey additional states. 
-
-The remaining 12 digits offer 1 million distinct dimensional threads for activity expansion. Dimensional Threads isolate and track those activities in the workflow that run in a cycle. They ensure that no naming collisions occur, even if the same activity is run multiple times. Each time duplex leg 2 of an activity returns with its payload, it can traverse the primary execution tree that remains (the remaining nodes in the graph); however, if the message includes a ‘pending’ status, it means that the channel will remain open, necessitating a dimensional execution thread be added to the flow, so that subsequent incoming messages can be tracked. This pattern likewise exists for `iterator` and `mark/goto` activities in that every adjacent activity that follows in the DAG will be uniquely addressed using a sequential dimensional thread that reflects its location in the collection being iterated.
-
-In the following series, [S] represents interactions with the STREAM while [D] represents interactions with the backend DATA STORE. The job begins with the trigger ( the entry point for the rooted tree). Every activity runs as a duplexed exchange with the request and response channels fully decoupled. 
-
-The trigger is unique, however, in that it does not execute Leg 1. This is because the outside caller is responsible for Leg 1, including generating the input data to be sent to the trigger to kick off the workflow.
-
-TRIGGER LEG 2
-
-```bash
-                  [D] a  A  | SET IF UNIQUE <JOBID> (ENSURE UNIQUE JOB ID)
-  888000001000001 [D] a  B  | SET TRIGGER STATE (SET TO 888000001000001)
-                  [S] b  C  | [SPAWN ADJACENT (CHILD) NODES]
-  999000000000000 [D] a  E  | PRESET SPAWNED ADJACENT NODE(S) ACTIVITY STATE
-                         F    => RETURN JOB ID TO CALLER
-WORKER ACTIVITY LEG 1
-                  [S] a a  | [DEQUEUE ACTIVITY]
-  999000000000000           *ACTIVITY STATUS WAS PRESET BY THE PARENT NODE*
-  ^-------------- [D] b c  | UPDATE ACTIVITY STATUS (DECREMENT to 899*)
-                             => FIX or CANCEL `IF < /^8\d+$/` [ACK/DELETE]
-                  [S] c d  | [ENQUEUE WORKER REQUEST]
-   ^------------- [D] b e  | UPDATE ACTIVITY STATUS (DECREMENT to 889*)
-                  [S] a f  | [ACK/DELETE]
-WORKER (SYNCHRONOUS | VARIANT 1 OF 2)
-                  [S] a  g  | [DEQUEUE WORKER REQUEST]
-  ^^^------------ [D] b  h  | QUERY ACTIVITY Status (CHECK IF JOB ACTIVE)
-                              => CANCEL `IF != /^889\d+$/` => [ACK/DELETE]
-                      X  X    => EXEC WORKER
-                  [S] d  j  | [ENQUEUE WORKER RESPONSE]
-                  [S] a  k  | [ACK/DELETE]
-WORKER (ASYNCHRONOUS | VARIANT 2 OF 2)
-                  [S] a  g  | [DEQUEUE WORKER REQUEST]
-  ^^^------------ [D] b  h  | QUERY ACTIVITY Status (CHECK IF JOB ACTIVE)
-                              => CANCEL `IF != /^889\d+$/` => [ACK/DELETE]
-                      X  X    => SAVE JOB METADATA | START WORKER
-                  [S] a  k  | [ACK/DELETE]
-                              => => =>
-                      X  X    => => => STOP WORKER (ALL DONE)
-                  [S] d  j  | [ENQUEUE WORKER RESPONSE]
-WORKER ACTIVITY LEG 2 (PROCESS PENDING | VARIANT 1 of 3)
-                  [S] a  l  | [DEQUEUE WORKER RESPONSE]
-     ^^^^^^------ [D] b  m  | INCREMENT DIMENSIONAL THREAD ENTRY COUNT by 1
-                              => CANCEL `IF != /^889\d+$/` => [ACK/DELETE]
-                  [S] c  n  | [ENQUEUE ADJACENT (CHILD) NODES]
-           ^^^^^^ [D] b  o  | INCREMENT DIMENSIONAL THREAD EXIT COUNT by 1
-  999000000000000 [D] b  q  | PRESET SPAWNED ADJACENT NODE(S) STATE
-                  [S] a  s  | [ACK/DELETE]
-WORKER ACTIVITY LEG 2 (PROCESS SUCCESS [OR CAUGHT ERROR] | VARIANT 2 of 3)
-                  [S] a  l  | [DEQUEUE WORKER RESPONSE]
-     ^^^^^^------ [D] b  m  | INCREMENT DIMENSIONAL THREAD ENTRY COUNT by 1
-                              => CANCEL `IF != /^889\d+$/` => [ACK/DELETE]
-                  [S] c  n  | [ENQUEUE ADJACENT (CHILD) NODES]
-           ^^^^^^ [D] b  o  | INCREMENT DIMENSIONAL THREAD EXIT COUNT by 1
-    ^------------ [D] b  p  | UPDATE ACTIVITY STATUS (DECREMENT to 888*)
-  999000000000000 [D] b  q  | PRESET SPAWNED ADJACENT NODE(S) STATE
-                  [S] d  r  | [ENQUEUE `JOB CLEANUP TASKS` IF JOB STATE = 0]
-                  [S] a  s  | [ACK/DELETE]
-WORKER ACTIVITY LEG 2 (PROCESS UNCAUGHT ERROR | VARIANT 3 of 3)
-                  [S] a  l  | [DEQUEUE WORKER RESPONSE]
-     ^^^^^^------ [D] b  m  | INCREMENT DIMENSIONAL THREAD ENTRY COUNT by 1
-                              => CANCEL `IF != /^\d{2}9\d+$/` => [ACK/DELETE]
-    ^------------ [D] b  p  | UPDATE ACTIVITY STATUS (DECREMENT to 887*)
-                  [S] d  r  | [ENQUEUE `JOB CLEANUP TASKS`]
-                  [S] a  s  | [ACK/DELETE]
-```
-
-Streams are used when executing an activity (such as transitioning to a child activity) as they guarantee that the child activity will be fully created and initialized before the request is marked for deletion. Even if the system has a catastrophic failure, the chain of custody can be guaranteed through the use of streams when the system comes online. If, for example, the system crashed during activity processing, the event history will reveal exactly where in the process it occurred, so that it is possible to restore state while still guaranteeing idempotency.

package/services/dimension/index.ts

@@ -1,39 +0,0 @@
-import { HotMeshGraph } from '../../types/hotmesh';
-
-class DimensionService {
-
-  //max int digit count that supports `hincrby`
-  static targetLength = 15; 
-
-  /**
-   * entry point for compiler-type activities. This is called by the compiler
-   * to bind the sorted activity IDs to the trigger activity. These are then used
-   * at runtime by the activities to track job/activity status.
-   * @param graphs
-   */
-  static compile(graphs: HotMeshGraph[]) {
-
-  }
-
-  /**
-   * All activities exist on a dimensional plane. Zero
-   * is the default and is implied if no dimension is
-   * present in the hash item key. EVERY value in the
-   * job ledger is dimensionalized even if the dimension
-   * is not present. The key, `AaA`, might not contain
-   * a dimensional index, but it is still implicitly
-   * dimensionalized as `AaA,0` (assuming a trigger).
-   * A value of `AxY,0,0,0,0,1,0,0` would reflect that
-   * an ancestor activity was dimensionalized beyond
-   * the default. The dimensional string must
-   * be included if not zero. There is likely a preceding
-   * sibling dimension, so it would not need to include
-   * the suffix, so these addresses are equivalent:
-   * `AxY,0,0,0,0,0,0,0` == `AxY` for said sibling.
-   */
-  static getSeed(index = 0): string {
-    return `,${index}`;
-  }
-}
-
-export { DimensionService };