querysub 0.337.0 → 0.339.0

package/package.json

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

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

@@ -1,3 +1,5 @@
+/// <reference path="../src.d.ts" />
+
 import { measureFnc } from "socket-function/src/profiling/measure";
 import { blue } from "socket-function/src/formatting/logColors";
 import { Archives } from "./archives";

package/src/2-proxy/PathValueProxyWatcher.ts

@@ -1541,7 +1541,7 @@ export class PathValueProxyWatcher {
 
                 let maxLocks = watcher.options.maxLocksOverride || DEFAULT_MAX_LOCKS;
                 if (locks.length > maxLocks) {
-                    throw new Error(`Too many locks for ${watcher.debugName} (${locks.length} > ${maxLocks}). You can override max locks with maxLocksOverride (in options / functionMetadata).`);
+                    throw new Error(`Too many locks for ${watcher.debugName} (${locks.length} > ${maxLocks}). Use Querysub.noLocks(() => ...) around code that is accessing too many values, assuming you don't want to lock them. You can override max locks with maxLocksOverride (in options / functionMetadata).`);
                 }
 
                 setValues = clientWatcher.setValues({

package/src/4-querysub/Querysub.ts

@@ -446,7 +446,8 @@ export class Querysub {
     }
 
     public static noLocks = (callback: () => void) => {
-        doProxyOptions({ noLocks: true }, callback);
+        // I don't think there's really any reason to use the regular no-locks, as it's only for local paths, but... I think we don't use locks for local paths anyway?
+        doProxyOptions({ unsafeNoLocks: true }, callback);
     };
 
     /** A more powerful version of omCommitFinished, which even waits for call predictions (or tries to).

package/src/deployManager/setupMachineMain.ts

@@ -276,6 +276,14 @@ async function main() {
         console.log("✅ Yarn installed");
     }
 
+    console.log("Setting timezone to America/New_York...");
+    await runPromise(`ssh ${sshRemote} "sudo timedatectl set-timezone America/New_York"`);
+    console.log("✅ Timezone set to America/New_York");
+
+    console.log(`Setting tmux scrollback history to 100000...`);
+    await runPromise(`ssh ${sshRemote} "tmux set-option -g history-limit 100000"`);
+    console.log("✅ Tmux scrollback history set to 100000");
+
     // 5. Clone current repo into ~/machine-alwaysup with SSH key handling for private repos
     console.log("Setting up repository...");
     let gitURLLive = await getGitURLLive();

package/src/diagnostics/logs/lifeCycleAnalysis/spec.md

@@ -4,7 +4,7 @@ Very small amount of data
     https://127-0-0-1.querysubtest.com:7007/?hot&enableLogs&page=login&filter=%22431%22&showingmanagement&endTime=1755140880000&startTime=1754950020000&managementpage=LogViewer2
 
 
-AFTER digests, go back to adding application code, as the framework is getting boring...
+BUG: Digest email isn't limitting per file? We got 12 from a single file?
 
 5) Life cycle analyzer
     - Implement regular range lifecycles first (matching an === object field)
@@ -85,6 +85,31 @@ DEBUG: Deploy hash updates.
 DEBUG: Suppression creation propagation 
     - It didn't propagate to all the servers?
 
+DEBUG: Machine always up script not restoring dead node?
+    - Add lifecycle for service launching + checking
+    - Does it just not restart killed services... at all?
+    - Maybe machine always up just gets in a bad state (maybe the main loop exits?)
+        - But it's an infinite loop, so it can't?
+
+DEBUG: Why we would get into an infinite identify loop:
+    Identified (loading) f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority for:
+        =-.,querysubtest._com.,/
+    Waiting for 1 authorities to be ready:
+        =-.,querysubtest._com.,/
+    Starting to identify f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority
+    Identified (loading) f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority for:
+        =-.,querysubtest._com.,/
+    Waiting for 1 authorities to be ready:
+        =-.,querysubtest._com.,/
+    Starting to identify f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority
+    Identified (loading) f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority for:
+        =-.,querysubtest._com.,/
+    Starting to identify f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority
+    Identified (loading) f194b2e77661e660.a794fbcf7b104c68.querysubtest.com:34139 as a path authority for:
+        =-.,querysubtest._com.,/
+IMPORTANT! The infinite identify loop causes servers to never finish identification, and so new PathValueServers couldn't start. SO THIS IS A REALLY BIG ISSUE!
+    - Restarting the server fixed it. I'm not sure if it was one service, or all of them?
+
 SPECIAL UI links for certain errors in log view
     - Probably dynamically created, based on contents of log
     - LINKS to filters for all these special errors on a special page