@hotmeshio/hotmesh 0.0.2 → 0.0.3

package/README.md

@@ -1,7 +1,7 @@
 # HotMesh
 ![alpha release](https://img.shields.io/badge/release-alpha-yellow)
 
-Build sophisticated, durable workflows without the overhead of a dedicated server cluster. With HotMesh, your code remains front and center using [infrastructure](./docs/faq.md#what-is-hotmesh) you already own.
+Build sophisticated, durable workflows without the overhead of a dedicated server cluster. With HotMesh, your code remains front and center using [infrastructure](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/faq.md#what-is-hotmesh) you already own.
 
 ## Install
 [![npm version](https://badge.fury.io/js/%40hotmeshio%2Fhotmesh.svg)](https://badge.fury.io/js/%40hotmeshio%2Fhotmesh)
@@ -98,7 +98,7 @@ run().catch((err) => {
 });
 ```
 
->HotMesh delivers durable function execution using a swarm of [distributed engines](./docs/distributed_orchestration.md). The design  consumes leftover CPU on your microservices to execute workflows without the cost and complexity of a central server.
+>HotMesh delivers durable function execution using a swarm of [distributed engines](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/distributed_orchestration.md). The design  consumes leftover CPU on your microservices to execute workflows without the cost and complexity of a central server.
 
 ## Advanced Design
 HotMesh's TypeScript SDK is the easiest way to make your functions durable. But if you need full control over your function lifecycles (including high-volume, high-speed use cases), you can use HotMesh's underlying YAML models to optimize your durable workflows. The following model depicts a sequence of activities orchestrated by HotMesh. Any function you associate with a `topic` in your YAML definition is guaranteed to be durable.
@@ -208,34 +208,34 @@ const hotMesh = await HotMesh.init({
 ```
 
 ### Observability
-Workflows and activities are run according to the rules you define, offering [Graph-Oriented](./docs/system_lifecycle.md#telemetry) telemetry insights into your legacy function executions.
+Workflows and activities are run according to the rules you define, offering [Graph-Oriented](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/system_lifecycle.md#telemetry) telemetry insights into your legacy function executions.
 
 ## FAQ
-Refer to the [FAQ](./docs/faq.md) for terminology, definitions, and an exploration of how HotMesh facilitates orchestration use cases.
+Refer to the [FAQ](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/faq.md) for terminology, definitions, and an exploration of how HotMesh facilitates orchestration use cases.
 
 ## Quick Start
-Refer to the [Quick Start](./docs/quickstart.md) for sample flows you can easily copy, paste, and modify to get started.
+Refer to the [Quick Start](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/quickstart.md) for sample flows you can easily copy, paste, and modify to get started.
 
 ## Developer Guide
-For more details on the complete development process, including information about schemas, APIs, and deployment, consult the [Developer Guide](./docs/developer_guide.md).
+For more details on the complete development process, including information about schemas, APIs, and deployment, consult the [Developer Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/developer_guide.md).
 
 ## Model Driven Development
-[Model Driven Development](./docs/model_driven_development.md) is an established strategy for managing process-oriented tasks. Check out this guide to understand its foundational principles.
+[Model Driven Development](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/model_driven_development.md) is an established strategy for managing process-oriented tasks. Check out this guide to understand its foundational principles.
 
 ## Data Mapping
-Exchanging data between activities is central to HotMesh. For detailed information on supported functions and the functional mapping syntax (@pipes), see the [Data Mapping Overview](./docs/data_mapping.md).
+Exchanging data between activities is central to HotMesh. For detailed information on supported functions and the functional mapping syntax (@pipes), see the [Data Mapping Overview](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/data_mapping.md).
 
 ## Composition
-While the simplest graphs are linear, detailing a consistent sequence of non-cyclical activities, graphs can be layered to represent intricate business scenarios. Some can even be designed to accommodate long-lasting workflows that span months. For more details, check out the [Composable Workflow Guide](./docs/composable_workflow.md).
+While the simplest graphs are linear, detailing a consistent sequence of non-cyclical activities, graphs can be layered to represent intricate business scenarios. Some can even be designed to accommodate long-lasting workflows that span months. For more details, check out the [Composable Workflow Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/composable_workflow.md).
 
 ## Architectural First Principles
-For a deep dive into HotMesh's distributed orchestration philosophy, refer to the [Architectural First Principles Overview](./docs/architecture.md).
+For a deep dive into HotMesh's distributed orchestration philosophy, refer to the [Architectural First Principles Overview](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/architecture.md).
 
 ## Distributed Orchestration
-HotMesh is a distributed orchestration engine. Refer to the [Distributed Orchestration Guide](./docs/distributed_orchestration.md) for a detailed breakdown of the approach.
+HotMesh is a distributed orchestration engine. Refer to the [Distributed Orchestration Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/distributed_orchestration.md) for a detailed breakdown of the approach.
 
 ## System Lifecycle
-Gain insight into the HotMesh's monitoring, exception handling, and alarm configurations via the [System Lifecycle Guide](./docs/system_lifecycle.md).
+Gain insight into the HotMesh's monitoring, exception handling, and alarm configurations via the [System Lifecycle Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/system_lifecycle.md).
 
 ## Alpha Release
-So what exacty is an [alpha release](./docs/alpha.md)?!
+So what exacty is an [alpha release](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/alpha.md)?!

package/build/package.json

@@ -1,14 +1,14 @@
 {
     "name": "@hotmeshio/hotmesh",
-    "version": "0.0.2",
+    "version": "0.0.3",
     "description": "Durable Workflows",
     "main": "build/index.js",
     "types": "build/index.d.ts",
     "repository": {
         "type": "git",
-        "url": "https://github.com/hotmeshio/hotmesh.git"
+        "url": "https://github.com/hotmeshio/sdk-typescript.git"
     },
-    "homepage": "https://github.com/hotmeshio/hotmesh#readme",
+    "homepage": "https://github.com/hotmeshio/sdk-typescript#readme",
     "publishConfig": {
         "access": "public"
     },

package/build/services/durable/client.d.ts

@@ -1,6 +1,6 @@
-import { WorkflowHandleService } from "./handle";
-import { HotMeshService as HotMesh } from "../hotmesh";
-import { ClientConfig, Connection, WorkflowOptions } from "../../types/durable";
+import { WorkflowHandleService } from './handle';
+import { HotMeshService as HotMesh } from '../hotmesh';
+import { ClientConfig, Connection, WorkflowOptions } from '../../types/durable';
 export declare class ClientService {
     connection: Connection;
     options: WorkflowOptions;

package/build/services/durable/client.js

@@ -92,7 +92,16 @@ class ClientService {
                 await hotMesh.activate(version);
             }
             catch (err) {
-                hotMesh.engine.logger.error('durable-client-workflow-activation-err', err);
+                hotMesh.engine.logger.error('durable-client-deploy-activate-err', err);
+                throw err;
+            }
+        }
+        else if (app && !app.active) {
+            try {
+                await hotMesh.activate(version);
+            }
+            catch (err) {
+                hotMesh.engine.logger.error('durable-client-activate-err', err);
                 throw err;
             }
         }

package/build/services/durable/worker.js

@@ -73,7 +73,16 @@ class WorkerService {
                 await hotMesh.activate(version);
             }
             catch (err) {
-                hotMesh.engine.logger.error('durable-worker-workflow-activation-error', err);
+                hotMesh.engine.logger.error('durable-worker-deploy-activate-err', err);
+                throw err;
+            }
+        }
+        else if (app && !app.active) {
+            try {
+                await hotMesh.activate(version);
+            }
+            catch (err) {
+                hotMesh.engine.logger.error('durable-worker-activate-err', err);
                 throw err;
             }
         }
@@ -176,7 +185,16 @@ class WorkerService {
                 await hotMesh.activate(version);
             }
             catch (err) {
-                console.log('durable-worker-activity-workflow-activation-error', err);
+                console.log('durable-worker-activity-deploy-activate-error', err);
+                throw err;
+            }
+        }
+        else if (app && !app.active) {
+            try {
+                await hotMesh.activate(version);
+            }
+            catch (err) {
+                hotMesh.engine.logger.error('durable-worker-activity-activate-err', err);
                 throw err;
             }
         }

package/build/services/store/index.js

@@ -238,7 +238,12 @@ class StoreService {
             app = {};
             for (const field in sApp) {
                 try {
-                    app[field] = sApp[field];
+                    if (field === 'active') {
+                        app[field] = sApp[field] === 'true';
+                    }
+                    else {
+                        app[field] = sApp[field];
+                    }
                 }
                 catch (e) {
                     app[field] = sApp[field];

package/build/types/hotmesh.d.ts

@@ -1,8 +1,8 @@
-import { ILogger } from "../services/logger";
-import { HotMeshService } from "../services/hotmesh";
-import { HookRules } from "./hook";
-import { RedisClass, RedisClient, RedisOptions } from "./redis";
-import { StreamData, StreamDataResponse } from "./stream";
+import { ILogger } from '../services/logger';
+import { HotMeshService } from '../services/hotmesh';
+import { HookRules } from './hook';
+import { RedisClass, RedisClient, RedisOptions } from './redis';
+import { StreamData, StreamDataResponse } from './stream';
 type HotMesh = typeof HotMeshService;
 type RedisConfig = {
     class: RedisClass;

package/package.json

@@ -1,14 +1,14 @@
 {
   "name": "@hotmeshio/hotmesh",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "description": "Durable Workflows",
   "main": "build/index.js",
   "types": "build/index.d.ts",
   "repository": {
     "type": "git",
-    "url": "https://github.com/hotmeshio/hotmesh.git"
+    "url": "https://github.com/hotmeshio/sdk-typescript.git"
   },
-  "homepage": "https://github.com/hotmeshio/hotmesh#readme",
+  "homepage": "https://github.com/hotmeshio/sdk-typescript#readme",
   "publishConfig": {
     "access": "public"
   },

package/services/durable/client.ts

@@ -1,8 +1,8 @@
-import { WorkflowHandleService } from "./handle";
-import { HotMeshService as HotMesh } from "../hotmesh";
-import { ClientConfig, Connection, WorkflowOptions } from "../../types/durable";
-import { getWorkflowYAML } from "./factory";
-import { JobState } from "../../types/job";
+import { WorkflowHandleService } from './handle';
+import { HotMeshService as HotMesh } from '../hotmesh';
+import { ClientConfig, Connection, WorkflowOptions } from '../../types/durable';
+import { getWorkflowYAML } from './factory';
+import { JobState } from '../../types/job';
 
 /*
 Here is an example of how the methods in this file are used:
@@ -101,7 +101,14 @@ export class ClientService {
         await hotMesh.deploy(getWorkflowYAML(workflowTopic, version));
         await hotMesh.activate(version);
       } catch (err) {
-        hotMesh.engine.logger.error('durable-client-workflow-activation-err', err);
+        hotMesh.engine.logger.error('durable-client-deploy-activate-err', err);
+        throw err;
+      }
+    } else if(app && !app.active) {
+      try {
+        await hotMesh.activate(version);
+      } catch (err) {
+        hotMesh.engine.logger.error('durable-client-activate-err', err);
         throw err;
       }
     }

package/services/durable/worker.ts

@@ -67,7 +67,14 @@ export class WorkerService {
         await hotMesh.deploy(factory(topic, version));
         await hotMesh.activate(version);
       } catch (err) {
-        hotMesh.engine.logger.error('durable-worker-workflow-activation-error', err);
+        hotMesh.engine.logger.error('durable-worker-deploy-activate-err', err);
+        throw err;
+      }
+    } else if(app && !app.active) {
+      try {
+        await hotMesh.activate(version);
+      } catch (err) {
+        hotMesh.engine.logger.error('durable-worker-activate-err', err);
         throw err;
       }
     }
@@ -176,7 +183,14 @@ export class WorkerService {
         await hotMesh.deploy(getActivityYAML(activityTopic, version));
         await hotMesh.activate(version);
       } catch (err) {
-        console.log('durable-worker-activity-workflow-activation-error', err);
+        console.log('durable-worker-activity-deploy-activate-error', err);
+        throw err;
+      }
+    } else if(app && !app.active) {
+      try {
+        await hotMesh.activate(version);
+      } catch (err) {
+        hotMesh.engine.logger.error('durable-worker-activity-activate-err', err);
         throw err;
       }
     }

package/services/store/index.ts

@@ -310,7 +310,11 @@ abstract class StoreService<T, U extends AbstractRedisClient> {
       app = {};
       for (const field in sApp) {
         try {
-          app[field] = sApp[field];
+          if (field === 'active') {
+            app[field] = sApp[field] === 'true';
+          } else {
+            app[field] = sApp[field];
+          }
         } catch (e) {
           app[field] = sApp[field];
         }

package/types/hotmesh.ts

@@ -1,8 +1,8 @@
-import { ILogger } from "../services/logger";
-import { HotMeshService } from "../services/hotmesh";
-import { HookRules } from "./hook";
-import { RedisClass, RedisClient, RedisOptions } from "./redis";
-import { StreamData, StreamDataResponse } from "./stream";
+import { ILogger } from '../services/logger';
+import { HotMeshService } from '../services/hotmesh';
+import { HookRules } from './hook';
+import { RedisClass, RedisClient, RedisOptions } from './redis';
+import { StreamData, StreamDataResponse } from './stream';
 
 type HotMesh = typeof HotMeshService;