querysub 0.359.0 → 0.360.0

package/package.json

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

package/src/config.ts

@@ -22,7 +22,12 @@ let yargObj = parseArgsFactory()
     // TODO: The bootstrapper is a single file. Maybe we shouldn't run the entire service just for that. Although... maybe it's fine, as services are light?
     .option("bootstraponly", { type: "boolean", desc: "Don't register as an edge node, so we serve the bootstrap files, but we don't need up to date code because we are not used for endpoints or the UI." })
     .option("notifyemails", { type: "array", desc: "The emails to notify when errors occur." })
-    .option("diskaudit", { type: "boolean", desc: "Track all audit logs to disk. This might end up writing A LOT of data." })
+    .option("diskaudit", {
+        type: "boolean",
+        // NOTE: I wanna see how long I can keep this on for. Eventually it's gonna become a problem and we're gonna have to turn it off. But for testing it's certainly useful as we don't know exactly what is gonna cause a problem. But it probably will be synchronization related, and every server does synchronization.
+        default: true,
+        desc: "Track all audit logs to disk. This might end up writing A LOT of data."
+    })
     .argv
     ;
 type QuerysubConfig = {

package/src/diagnostics/logs/IndexedLogs/LogViewer3.tsx

@@ -23,6 +23,7 @@ import { PUBLIC_MOVE_THRESHOLD } from "./BufferIndexLogsOptimizationConstants";
 import { atomic } from "../../../2-proxy/PathValueProxyWatcher";
 import { errorToUndefined } from "querysub/src/errors";
 import { IndexedLogResults, createEmptyIndexedLogResults } from "./BufferIndexHelpers";
+import { TimeFilePath } from "./TimeFileTree";
 
 let searchText = new URLParam("searchText", "");
 let readLiveData = new URLParam("readLiveData", false);
@@ -435,6 +436,19 @@ export class LogViewer3 extends qreact.Component {
             this.state.paths = allPaths;
             this.state.loadingPaths = false;
         });
+        return allPaths;
+    }
+
+    async updatePaths() {
+        let prevPaths = this.getPaths();
+        let newPaths = await this.loadPaths();
+        Querysub.commitLocal(() => {
+            function getHash(path: TimeFilePath): string {
+                return path.threadId + "_" + path.machineId;
+            }
+            let keep = new Set(prevPaths.map(getHash));
+            this.state.paths = newPaths?.filter(x => keep.has(getHash(x))) || [];
+        });
     }
 
     cancel = async () => {
@@ -798,11 +812,16 @@ export class LogViewer3 extends qreact.Component {
                         <Button
                             flavor="large"
                             onClick={() => void this.loadPaths()}
-                            hue={120}
+                            hue={this.state.paths.length ? 200 : 120}
                         >
-                            Preview Files
+                            {this.state.paths.length && "Reset Files" || "Preview Files"}
                         </Button>
                     )}
+                    {this.state.paths && !savedPathsURL.value &&
+                        <Button flavor="large" hue={120} onClick={() => void this.updatePaths()}>
+                            Update Files
+                        </Button>
+                    }
                     {savedPathsURL.value && (
                         <Button
                             flavor="large"

package/src/diagnostics/logs/lifeCycleAnalysis/lifeCycles.tsx

@@ -19,8 +19,7 @@ IMPORTANT! Now I am properly calling shutdown, so none of the streamed logs shou
 
 
 
-OH! The archives have to be put in the home folder. They aren't?
-
+Logs still aren't appearing. Hmm...
 
 Hmm... why are not enough logs appearing?
     - We only have logs for server.ts? Wtf?