querysub 0.667.0 → 0.669.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "querysub",
-  "version": "0.667.0",
+  "version": "0.669.0",
   "main": "index.js",
   "license": "MIT",
   "note1": "note on node-forge fork, see https://github.com/digitalbazaar/forge/issues/744 for details",

package/src/deployManager/emergencyUpdateMain.ts

@@ -8,6 +8,9 @@ import { green, magenta } from "socket-function/src/formatting/logColors";
 import { delay } from "socket-function/src/batching";
 import { MachineServiceControllerBase, ServiceConfig } from "./machineSchema";
 import { initArchives2 } from "../-a-archives/archives2";
+import { getMachineId, getOwnThreadId } from "sliftutils/misc/https/certs";
+import { getDomain } from "../config";
+import { getOwnMachineId } from "sliftutils/misc/https/certs";
 
 // setServiceConfigs notifies the machines without awaiting the notifications, so we linger before exiting to let them go out. If they are lost anyway (ex, the machines are unreachable), the machines still pick up the new configs on their fallback resync poll.
 const NOTIFY_GRACE_PERIOD = 10 * 1000;
@@ -15,6 +18,13 @@ const NOTIFY_GRACE_PERIOD = 10 * 1000;
 // The emergency workflow from the services list page, as one command: commit/publish/push querysub, commit/push the service repo, then point every service config at the new commit with no overlap. Everything here writes to the service configs archives directly, which falls back to backblaze, so this works while the storage servers (and therefore the deploy pages) are down.
 async function main() {
     disablePathAuditer();
+    require("debugbreak")(2);
+    debugger;
+
+    console.log({
+        machineId: getOwnMachineId(getDomain()),
+        threadId: getOwnThreadId(getDomain()),
+    })
 
     let controller = new MachineServiceControllerBase();
     let commitMessage = `emergency update ${formatDateTime(Date.now())}`;