@harperfast/harper-pro 5.0.0-beta.2 → 5.0.0-beta.3

package/core/integrationTests/README.md

@@ -184,7 +184,7 @@ Integration test utilities are located in the [`integrationTests/utils/`](./util
 
 The most commonly used utilities are:
 
-- **`setupHarper(context)`** - Sets up a complete Harper instance for testing. Use in `before()` hooks.
+- **`startHarper(context)`** - Sets up a complete Harper instance for testing. Use in `before()` hooks.
 - **`teardownHarper(context)`** - Tears down a Harper instance and cleans up resources. Use in `after()` hooks.
 - **`ContextWithHarper`** - TypeScript interface for test context with Harper instance details.
 - **`targz(dirPath)`** - Compresses a directory into a base64-encoded tar.gz string for application deployment.
@@ -193,11 +193,11 @@ The most commonly used utilities are:
 
 ```ts
 import { suite, test, before, after } from 'node:test';
-import { setupHarper, teardownHarper, type ContextWithHarper } from './utils/harperLifecycle.mts';
+import { startHarper, teardownHarper, type ContextWithHarper } from './utils/harperLifecycle.ts';
 
 suite('test suite', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx);
+		await startHarper(ctx);
 	});
 
 	after(async () => {
@@ -227,12 +227,12 @@ Copy and paste the following content to get started:
  */
 import { suite, test, before, after } from 'node:test';
 import { strictEqual } from 'node:assert/strict';
-// Note: adjust the relative path accordingly (e.g., '../utils/harperLifecycle.mts')
-import { setupHarper, teardownHarper, type ContextWithHarper } from './utils/harperLifecycle.mts';
+// Note: adjust the relative path accordingly (e.g., '../utils/harperLifecycle.ts')
+import { startHarper, teardownHarper, type ContextWithHarper } from './utils/harperLifecycle.ts';
 
 suite('short description of tests', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx);
+		await startHarper(ctx);
 	});
 
 	after(async () => {

package/core/integrationTests/deploy/deploy-from-github.test.ts

@@ -5,7 +5,7 @@
  */
 import { suite, test, before, after } from 'node:test';
 import { deepStrictEqual, ok, strictEqual } from 'node:assert/strict';
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 import { join } from 'node:path';
 import { existsSync } from 'node:fs';
 import { readFile } from 'node:fs/promises';
@@ -13,7 +13,7 @@ import { parse } from 'yaml';
 
 suite('GitHub application deployment', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx);
+		await startHarper(ctx);
 	});
 
 	after(async () => {

package/core/integrationTests/deploy/deploy-from-source.test.ts

@@ -12,12 +12,12 @@ import { join } from 'node:path';
 import { existsSync } from 'node:fs';
 import { setTimeout as sleep } from 'node:timers/promises';
 
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 import { targz } from '../utils/targz.ts';
 
 suite('Local application deployment', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx);
+		await startHarper(ctx);
 	});
 
 	after(async () => {

package/core/integrationTests/server/crash-replay.test.ts

@@ -3,12 +3,12 @@
  * database, so replay needs to work for harper to startup.
  */
 import { suite, test, before, after } from 'node:test';
-import { setupHarper, teardownHarper, type ContextWithHarper, startHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 import { equal } from 'node:assert';
 
 suite('Transaction log replay on crash', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx, {
+		await startHarper(ctx, {
 			config: {},
 			env: {
 				HARPER_NO_FLUSH_ON_EXIT: true, // specifically don't flush, we are testing restart/replay and simulating a crash
@@ -28,7 +28,7 @@ suite('Transaction log replay on crash', (ctx: ContextWithHarper) => {
 		await startHarper(ctx);
 		let response = await sendOperation(ctx.harper, {
 			operation: 'list_roles',
-			authorization: ctx.admin,
+			authorization: ctx.harper.admin,
 		});
 		equal(response.length, 1);
 		equal(response[0].role, 'super_user');

package/core/integrationTests/server/operation-user-rbac.test.ts

@@ -11,7 +11,7 @@
 import { suite, test, before, after } from 'node:test';
 import { strictEqual, ok } from 'node:assert/strict';
 
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 
 const DATABASE = 'test_db';
 const TABLE = 'dogs';
@@ -35,7 +35,7 @@ const STANDARD_USER_PASS = 'Test1234!';
 
 suite('operations RBAC', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx, { config: {}, env: {} });
+		await startHarper(ctx, { config: {}, env: {} });
 
 		const adminAuth = `Basic ${Buffer.from(`${ctx.harper.admin.username}:${ctx.harper.admin.password}`).toString('base64')}`;
 

package/core/integrationTests/server/operations-server.test.ts

@@ -12,11 +12,11 @@ import { ok, strictEqual } from 'node:assert/strict';
 import { pack, unpack } from 'msgpackr';
 import { encode, decode } from 'cbor-x';
 
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 
 suite('Operations Server', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx, { config: {}, env: {} });
+		await startHarper(ctx, { config: {}, env: {} });
 	});
 
 	after(async () => {
@@ -95,6 +95,7 @@ suite('Operations Server', (ctx: ContextWithHarper) => {
 				'Accept': 'application/json',
 				'Authorization': `Basic ${Buffer.from(`${ctx.harper.admin.username}:${ctx.harper.admin.password}`).toString('base64')}`,
 			},
+			// @ts-expect-error - Need to update fetch types to support `Buffer<ArrayBufferLike>`
 			body: pack({ operation: 'describe_all' }),
 		});
 		strictEqual(response.status, 200);
@@ -140,6 +141,7 @@ suite('Operations Server', (ctx: ContextWithHarper) => {
 				'Accept': 'application/json',
 				'Authorization': `Basic ${Buffer.from(`${ctx.harper.admin.username}:${ctx.harper.admin.password}`).toString('base64')}`,
 			},
+			// @ts-expect-error - Need to update fetch types to support `Buffer<ArrayBufferLike>`
 			body: encode({ operation: 'describe_all' }),
 		});
 		strictEqual(response.status, 200);

package/core/integrationTests/server/storage-reclamation.test.ts

@@ -20,7 +20,7 @@ import { suite, test, before, after } from 'node:test';
 import { ok, strictEqual } from 'node:assert/strict';
 import { setTimeout as sleep } from 'node:timers/promises';
 
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 
 const TEST_DATABASE = 'test';
 const TEST_TABLE = 'reclaim';
@@ -29,7 +29,7 @@ suite('Storage reclamation', (ctx: ContextWithHarper) => {
 	before(async () => {
 		// Set a very high reclamation threshold (99%) so reclamation triggers immediately
 		// and a short interval (1 second) for faster test execution
-		await setupHarper(ctx, {
+		await startHarper(ctx, {
 			config: {
 				STORAGE_RECLAMATION_THRESHOLD: 0.99,
 				STORAGE_RECLAMATION_INTERVAL: '1s',

package/core/integrationTests/server/thread-management.test.ts

@@ -8,11 +8,11 @@
 import { suite, test, before, after } from 'node:test';
 import { strictEqual } from 'node:assert/strict';
 
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 
 suite('Thread Management', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx, { config: {}, env: {} });
+		await startHarper(ctx, { config: {}, env: {} });
 	});
 
 	after(async () => {

package/core/integrationTests/utils/README.md

@@ -4,26 +4,41 @@ This directory contains utility functions and modules for Harper integration tes
 
 ## Table of Contents
 
-- [Harper Lifecycle Management](#harper-lifecycle-management)
-- [Loopback Address Pool](#loopback-address-pool)
-- [Compression Utilities](#compression-utilities)
+- [Integration Test Utilities](#integration-test-utilities)
+  - [Table of Contents](#table-of-contents)
+  - [Harper Lifecycle Management](#harper-lifecycle-management)
+    - [`startHarper(context, options?): Promise<ContextWithHarper>`](#startharpercontext-options-promisecontextwithharper)
+    - [`StartHarperOptions`](#startharperoptions)
+    - [`killHarper(context): Promise<void>`](#killharpercontext-promisevoid)
+    - [`teardownHarper(context): Promise<void>`](#teardownharpercontext-promisevoid)
+    - [`ContextWithHarper`](#contextwithharper)
+  - [Loopback Address Pool](#loopback-address-pool)
+    - [`validateLoopbackAddressPool(): Promise<ValidationResult>`](#validateloopbackaddresspool-promisevalidationresult)
+    - [`getNextAvailableLoopbackAddress(): Promise<string>`](#getnextavailableloopbackaddress-promisestring)
+    - [`releaseLoopbackAddress(address: string): Promise<void>`](#releaseloopbackaddressaddress-string-promisevoid)
+    - [`releaseAllLoopbackAddressesForCurrentProcess(): Promise<void>`](#releaseallloopbackaddressesforcurrentprocess-promisevoid)
+  - [Compression Utilities](#compression-utilities)
+    - [`targz(dirPath: string): Promise<string>`](#targzdirpath-string-promisestring)
+  - [Scripts](#scripts)
+    - [`scripts/setup-loopback.sh`](#scriptssetup-loopbacksh)
+    - [`scripts/run.mts`](#scriptsrunmts)
 
 ---
 
 ## Harper Lifecycle Management
 
-**Module:** [`harperLifecycle.mts`](./harperLifecycle.mts)
+**Module:** [`harperLifecycle.ts`](./harperLifecycle.ts)
 
 Provides functions for managing Harper instances during integration tests, including installation, startup, and teardown.
 
-### `setupHarper(context, options?): Promise<ContextWithHarper>`
+### `startHarper(context, options?): Promise<ContextWithHarper>`
 
 Sets up a complete Harper instance for testing.
 
 **Parameters:**
 
 - `context` - [`ContextWithHarper`](#contextwithharper) - The test context object
-- `options` - [`SetupHarperOptions`](#setupharperoptions) (optional) - Configuration options for the setup process
+- `options` - [`StartHarperOptions`](#startharperoptions) (optional) - Configuration options for the setup process
 
 **Returns:** `Promise<ContextWithHarper>` - The context with the `harper` property populated
 
@@ -31,8 +46,8 @@ Sets up a complete Harper instance for testing.
 
 This method should be used in the `before()` lifecycle hook for a test suite. It performs the following steps:
 
-1. Creates a Harper instance in a temporary directory
-2. Assigns a unique loopback address from the loopback address pool
+1. Creates a Harper instance in a temporary directory (reuses `ctx.harper.installDir` if already set)
+2. Assigns a unique loopback address from the loopback address pool (reuses `ctx.harper.hostname` if already set)
 3. Starts Harper with test configuration (which self-installs)
 4. Waits for Harper to be fully started, waiting for the startup message to appear in stdout
 5. Populates the `context.harper` object with connection details
@@ -43,12 +58,12 @@ This method should be used in the `before()` lifecycle hook for a test suite. It
 
 ```ts
 import { suite, test, before, after } from 'node:test';
-import { setupHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.mts';
+import { startHarper, teardownHarper, type ContextWithHarper } from '../utils/harperLifecycle.ts';
 
 // Default setup
 suite('My test suite', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx);
+		await startHarper(ctx);
 	});
 
 	after(async () => {
@@ -64,12 +79,12 @@ suite('My test suite', (ctx: ContextWithHarper) => {
 
 ---
 
-### `SetupHarperOptions`
+### `StartHarperOptions`
 
-Configuration options for `setupHarper()`.
+Configuration options for `startHarper()`.
 
 ```typescript
-export interface SetupHarperOptions {
+export interface StartHarperOptions {
 	startupTimeoutMs?: number;
 	config: any;
 	env: any;
@@ -78,13 +93,44 @@ export interface SetupHarperOptions {
 
 **Properties:**
 
-- **`config`** - `object` (optional) - Additional configuration options to pass to the Harper CLI.
-- **`env`** - `object` (optional) - Additional environment variables to set when starting Harper.
+- **`config`** - `object` - Additional configuration options to pass to the Harper CLI.
+- **`env`** - `object` - Additional environment variables to set when starting Harper.
 - **`startupTimeoutMs`** - `number` (optional) - Timeout in milliseconds to wait for Harper to start. Defaults to 30000, or the value of the `HARPER_INTEGRATION_TEST_STARTUP_TIMEOUT_MS` environment variable if set.
 
 **Environment Variables:**
 
-- `HARPER_INTEGRATION_TEST_STARTUP_TIMEOUT_MS` - Sets the default startup delay for all tests when `startupTimeoutMs` is not explicitly provided
+- `HARPER_INTEGRATION_TEST_STARTUP_TIMEOUT_MS` - Sets the default startup timeout for all tests when `startupTimeoutMs` is not explicitly provided
+- `HARPER_INTEGRATION_TEST_INSTALL_PARENT_DIR` - Override the parent directory for Harper installation directories (defaults to the OS temp directory)
+- `HARPER_INTEGRATION_TEST_INSTALL_SCRIPT` - Override the path to the Harper CLI script (defaults to `dist/bin/harper.js` relative to the repo root)
+- `HARPER_INTEGRATION_TEST_LOG_DIR` - When set, stdout/stderr logs and Harper's `hdb.log` are written to per-suite subdirectories here; logs are deleted automatically on successful exit and retained on failure
+
+---
+
+### `killHarper(context): Promise<void>`
+
+Kills the running Harper process. Does **not** release the loopback address or remove the installation directory.
+
+**Parameters:**
+
+- `context` - [`ContextWithHarper`](#contextwithharper) - The test context with a running Harper instance
+
+**Returns:** `Promise<void>`
+
+**Description:**
+
+Sends `SIGTERM` to the Harper process and waits for it to exit. If the process does not exit within 200ms, `SIGKILL` is sent.
+
+This is useful for testing Harper restart/crash scenarios. After calling `killHarper()`, call `startHarper()` to restart the instance in the same directory with the same loopback address.
+
+**Example:**
+
+```ts
+test('recovers after restart', async () => {
+	await killHarper(ctx);
+	await startHarper(ctx);
+	// Harper is running again on the same address
+});
+```
 
 ---
 
@@ -100,7 +146,7 @@ Tears down a Harper instance and cleans up all resources.
 
 **Description:**
 
-This method should be used in the `after()` lifecycle hook in conjunction with `setupHarper()` and `before()`. It performs the following cleanup steps:
+This method should be used in the `after()` lifecycle hook in conjunction with `startHarper()` and `before()`. It performs the following cleanup steps:
 
 1. Stops the Harper instance
 2. Releases the loopback address back to the pool
@@ -111,7 +157,7 @@ This method should be used in the `after()` lifecycle hook in conjunction with `
 ```ts
 suite('My test suite', (ctx: ContextWithHarper) => {
 	before(async () => {
-		await setupHarper(ctx);
+		await startHarper(ctx);
 	});
 
 	after(async () => {
@@ -131,23 +177,27 @@ TypeScript interface that extends `SuiteContext` and `TestContext` from Node.js
 **Interface Definition:**
 
 ```typescript
-interface ContextWithHarper extends SuiteContext, TestContext {
-	harper: {
-		installDir: string;
-		admin: {
-			username: string;
-			password: string;
-		};
-		httpURL: string;
-		operationsAPIURL: string;
-		loopbackAddress: string;
+export interface HarperContext {
+	installDir: string;
+	admin: {
+		username: string;
+		password: string;
 	};
+	httpURL: string;
+	operationsAPIURL: string;
+	hostname: string;
+	process: ChildProcess;
+	logDir?: string;
+}
+
+export interface ContextWithHarper extends SuiteContext, TestContext {
+	harper: HarperContext;
 }
 ```
 
 **Properties:**
 
-- **`harper`** - `object` - The Harper instance details
+- **`harper`** - `HarperContext` - The Harper instance details
   - **`installDir`** - `string` - The absolute path to the Harper installation directory
   - **`admin`** - `object` - Admin credentials
     - **`username`** - `string` - The Harper Admin Username (default: `'admin'`)
@@ -155,6 +205,8 @@ interface ContextWithHarper extends SuiteContext, TestContext {
   - **`httpURL`** - `string` - The HTTP URL for the Harper instance (e.g., `'http://127.0.0.2:9926'`)
   - **`operationsAPIURL`** - `string` - The Operations API URL (e.g., `'http://127.0.0.2:9925'`)
   - **`hostname`** - `string` - The assigned loopback IP address (e.g., `'127.0.0.2'`)
+  - **`process`** - `ChildProcess` - The Node.js child process handle for the running Harper instance
+  - **`logDir`** - `string | undefined` - Absolute path to the per-suite log directory; only set when `HARPER_INTEGRATION_TEST_LOG_DIR` is configured
 
 **Example Usage:**
 
@@ -175,7 +227,7 @@ test('authenticate with admin credentials', async () => {
 
 ## Loopback Address Pool
 
-**Module:** [`loopbackAddressPool.mts`](./loopbackAddressPool.mts)
+**Module:** [`loopbackAddressPool.ts`](./loopbackAddressPool.ts)
 
 Manages a pool of loopback addresses for concurrent test execution. This allows multiple Harper instances to run simultaneously on different loopback addresses without port conflicts.
 
@@ -227,7 +279,7 @@ If no addresses are available, the function waits and retries until one becomes
 **Pool file location:** `${tmpdir()}/harper-integration-test-loopback-pool.json`
 **Lock file location:** `${tmpdir()}/harper-integration-test-loopback-pool.lock`
 
-**Note:** This is automatically called by `setupHarper()`. You typically don't need to call this directly unless you're implementing custom test infrastructure.
+**Note:** This is automatically called by `startHarper()`. You typically don't need to call this directly unless you're implementing custom test infrastructure.
 
 ---
 
@@ -285,7 +337,7 @@ try {
 
 ## Compression Utilities
 
-**Module:** [`targz.mts`](./targz.mts)
+**Module:** [`targz.ts`](./targz.ts)
 
 Provides utilities for compressing directories into tar.gz archives.
 

package/core/integrationTests/utils/harperLifecycle.ts

@@ -18,7 +18,7 @@ const LOG_DIR = process.env.HARPER_INTEGRATION_TEST_LOG_DIR;
 /**
  * Options for setting up a Harper instance.
  */
-export interface SetupHarperOptions {
+export interface StartHarperOptions {
 	/**
 	 * Timeout in milliseconds to wait for Harper to start.
 	 * @default 30000
@@ -59,8 +59,8 @@ export interface HarperContext {
 /**
  * Test context interface with Harper instance details.
  *
- * This interface is populated by `setupHarper()` and contains all necessary
- * information to interact with the test Harper instance.
+ * This interface is populated by `startHarper()` and contains
+ * all necessary information to interact with the test Harper instance.
  */
 export interface ContextWithHarper extends SuiteContext, TestContext {
 	harper: HarperContext;
@@ -184,6 +184,10 @@ function runHarperCommand({ args, env, completionMessage, logDir }: RunHarperCom
  * This function performs installation, startup, and waits for Harper to be ready.
  * Always call `teardownHarper()` in the `after()` hook to clean up resources.
  *
+ * If `ctx.harper.installDir` or `ctx.harper.hostname` are already set they are
+ * reused rather than creating new ones — making this safe to call after
+ * `killHarper()` to restart an existing instance.
+ *
  * @param ctx - The test context to populate with Harper instance details
  * @param options - Optional configuration for the setup process
  * @returns The context with the `harper` property populated
@@ -192,7 +196,7 @@ function runHarperCommand({ args, env, completionMessage, logDir }: RunHarperCom
  * ```ts
  * suite('My tests', (ctx: ContextWithHarper) => {
  *   before(async () => {
- *     await setupHarper(ctx);
+ *     await startHarper(ctx);
  *   });
  *
  *   after(async () => {
@@ -206,19 +210,7 @@ function runHarperCommand({ args, env, completionMessage, logDir }: RunHarperCom
  * });
  * ```
  */
-export async function setupHarper(ctx: ContextWithHarper, options?: SetupHarperOptions): Promise<ContextWithHarper> {
-	return startHarper(ctx, options);
-}
-
-/**
- * Starts a Harper instance that has been installed.
- *
- * This is a lower-level function called by `setupHarper()`.
- * Most tests should use `setupHarper()` instead.
- *
- * @param ctx - The test context with Harper installation details
- */
-export async function startHarper(ctx: ContextWithHarper, options?: SetupHarperOptions): Promise<ContextWithHarper> {
+export async function startHarper(ctx: ContextWithHarper, options?: StartHarperOptions): Promise<ContextWithHarper> {
 	// Create a directory for this Harper installation
 	// Use the system temp directory by default, or a custom parent directory if specified
 	const installDirPrefix = join(
@@ -322,7 +314,7 @@ export async function killHarper(ctx: ContextWithHarper): Promise<void> {
  * ```ts
  * suite('My tests', (ctx: ContextWithHarper) => {
  *   before(async () => {
- *     await setupHarper(ctx);
+ *     await startHarper(ctx);
  *   });
  *
  *   after(async () => {

package/core/package.json

@@ -1,7 +1,7 @@
 {
 	"name": "harper",
 	"description": "Harper is an open-source Node.js performance platform that unifies database, cache, application, and messaging layers into one in-memory process.",
-	"version": "5.0.0-beta.1",
+	"version": "5.0.0-beta.3",
 	"license": "Apache-2.0",
 	"homepage": "https://harper.fast",
 	"bugs": {
@@ -133,7 +133,7 @@
 		"globals": "^16.5.0",
 		"intercept-stdout": "0.1.2",
 		"mkcert": "^3.2.0",
-		"mocha": "^11.7.4",
+		"mocha": "^11.7.5",
 		"mqtt": "~4.3.8",
 		"oxlint": "^1.31.0",
 		"prettier": "~3.7.3",
@@ -144,18 +144,18 @@
 		"tsx": "^4.20.6",
 		"typescript": "^5.8.2",
 		"typescript-eslint": "^8.45.0",
-		"undici": "^7.16.0",
+		"undici": "^7.24.4",
 		"why-is-node-still-running": "^1.0.0"
 	},
 	"dependencies": {
-		"@aws-sdk/client-s3": "3.964.0",
+		"@aws-sdk/client-s3": "^3.1012.0",
 		"@aws-sdk/lib-storage": "3.964.0",
 		"@datadog/pprof": "^5.11.1",
 		"@endo/static-module-record": "^1.1.2",
-		"@fastify/autoload": "5.10.0",
-		"@fastify/compress": "~6.5.0",
-		"@fastify/cors": "~9.0.1",
-		"@fastify/static": "~7.0.4",
+		"@fastify/autoload": "^6.3.1",
+		"@fastify/compress": "^8.3.1",
+		"@fastify/cors": "^11.2.0",
+		"@fastify/static": "^9.0.0",
 		"@harperfast/extended-iterable": "^1.0.1",
 		"@harperfast/rocksdb-js": "^0.1.12",
 		"@turf/area": "6.5.0",
@@ -179,8 +179,8 @@
 		"dotenv": "^16.4.7",
 		"easy-ocsp": "1.2.2",
 		"fast-glob": "3.3.3",
-		"fastify": "~4.29.0",
-		"fastify-plugin": "~4.5.1",
+		"fastify": "^5.8.2",
+		"fastify-plugin": "^5.1.0",
 		"fs-extra": "11.3.3",
 		"graphql": "^16.10.0",
 		"graphql-http": "^1.22.4",
@@ -194,7 +194,7 @@
 		"jsonata": "1.8.7",
 		"jsonwebtoken": "9.0.3",
 		"lmdb": "3.5.2",
-		"lodash": "4.17.21",
+		"lodash": "^4.17.23",
 		"mathjs": "11.12.0",
 		"micromatch": "^4.0.8",
 		"minimist": "1.2.8",
@@ -222,8 +222,8 @@
 		"ses": "^1.14.0",
 		"stream-chain": "2.2.5",
 		"stream-json": "1.9.1",
-		"systeminformation": "5.27.11",
-		"tar-fs": "3.0.9",
+		"systeminformation": "^5.31.4",
+		"tar-fs": "^3.1.2",
 		"ulidx": "0.5.0",
 		"uuid": "11.1.0",
 		"validate.js": "0.13.1",

package/core/server/threads/manageThreads.js

@@ -339,7 +339,9 @@ function onMessageByType(type, listener) {
 	listeners.push(listener);
 	if (messagesQueuedByType.has(type)) {
 		for (let message of messagesQueuedByType.get(type)) {
-			listener(message);
+			// enqueue in next event turn; messages always come as events, and trying to do this synchronously can be
+			// problematic for getting mixed up with module loading
+			setImmediate(() => listener(message));
 		}
 		messagesQueuedByType.delete(type);
 	}

package/dist/cloneNode/cloneNode.js

@@ -214,9 +214,6 @@ async function cloneNode() {
     if (freshClone || !systemExists) {
         await installHarper();
     }
-    // Start Harper to prepare for clone operations
-    const { main } = await import('../core/bin/run.js');
-    await main();
     logger.initLogSettings();
     harperLogger = logger.loggerWithTag('cloneNode');
     // Get the config from the leader and write it to the existing local config file, excluding any parameters that should not be cloned
@@ -241,10 +238,9 @@ async function cloneNode() {
             await databases.system.hdb_user.delete({ username: 'clone-temp-admin' });
         }
     }
-    // Restarting workers to ensure new configuration it loaded.
-    log('Restarting workers to apply new configuration');
-    const { restartWorkers } = await import('../core/server/threads/manageThreads.js');
-    await restartWorkers();
+    // Start Harper to prepare for clone operations
+    const { main } = await import('../core/bin/run.js');
+    await main();
     // Dynamically importing setNode because it was causing early usage of rootpath var install before it was initialized.
     const { setNode } = await import('../replication/setNode.js');
     // Set node will set up replication between this node and the leader,