querysub 0.623.0 → 0.625.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "querysub",
-  "version": "0.623.0",
+  "version": "0.625.0",
   "main": "index.js",
   "license": "MIT",
   "note1": "note on node-forge fork, see https://github.com/digitalbazaar/forge/issues/744 for details",
@@ -79,7 +79,7 @@
     "node-forge": "https://github.com/sliftist/forge#e618181b469b07bdc70b968b0391beb8ef5fecd6",
     "pako": "^2.1.0",
     "peggy": "^5.0.6",
-    "sliftutils": "^1.7.90",
+    "sliftutils": "^1.7.94",
     "socket-function": "^1.2.30",
     "terser": "^5.31.0",
     "typenode": "^6.6.1",

package/src/-a-archives/archives2.ts

@@ -76,14 +76,14 @@ function archiveBuilder(bucket: string, overrides: Partial<RemoteConfigBase>) {
                 // NOTE: Once we add new sources, we need to add something at a new start time in the future so we have time to move the files. 
                 // TODO: EVENTUALLY, Once we have enough data, instead of restriping, we need to bisect the data. That way we can slowly move over the data instead of trying to rewrite all of our data all at once. However, for the moment, moving all the data is probably fine. On the data center, we should be able to move terabytes of data every hour, so we should be able to handle quite a bit, especially if we have a few days to run the restriping. 
                 // IMPORTANT! Every time we re-stripe, we need to increment the route version. Otherwise, we could reuse a folder that we previously used that's no longer in sync. which will cause us to resurrect old data, which is very bad. We don't want to do that...
-                ...stripeSources([ONTARIO, HETZNER], { routeVersion: 1 }),
+                ...stripeSources([ONTARIO, HETZNER], { routeVersion: 2 }),
                 { type: "backblaze", url: BACKBLAZE, name: "backblaze" },
             ]
         },
     ]);
 
     return createArchives({
-        version: 23,
+        version: 25,
         sources,
     });
 }
@@ -202,6 +202,6 @@ export async function initArchives2() {
         getArchives2Public(""),
     ];
     for (let bucket of buckets) {
-        await bucket.hasWriteAccess()
+        await bucket.hasWriteAccess();
     }
 }

package/src/deployManager/emergencyUpdateMain.ts

@@ -7,6 +7,7 @@ import { formatDateTime } from "socket-function/src/formatting/format";
 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";
 
 // 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;
@@ -73,6 +74,8 @@ async function main() {
     await delay(NOTIFY_GRACE_PERIOD);
 
     console.log(green(`Emergency update complete: ${outdated.length} services updating to ${gitInfo.latestRef}`));
+
+    await initArchives2();
 }
 
 main().catch(logErrors).finally(() => process.exit());