querysub 0.510.0 → 0.511.0

package/package.json

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

package/spec.txt

@@ -1,8 +1,5 @@
-
 todonext
-Review the network trakcing code again.
-    - Maybe manually refactor it
-Ensure there is no dumb sync code
+Make sure the AI updates the machine schema in a smart way. So we can actually have both the old and the new servers config and manage them correctly. make sure if we make multiple updates, it still remembers what the old config is. And make sure deploy all works correctly. 
 
 
 

package/src/4-querysub/Querysub.ts

@@ -381,7 +381,9 @@ export class Querysub {
         }
         return result;
     }
+    /** @deprecated Don't use this. It doesn't do what you think. It can't be used for writes.  */
     public static localCommit = Querysub.localRead;
+    /** @deprecated Don't use this. It doesn't do what you think. It can't be used for writes.  */
     public static commitLocal = Querysub.localRead;
     public static fastRead<T>(fnc: () => T, options?: Partial<WatcherOptions<T>>) {
         return proxyWatcher.runOnce({

package/src/deployManager/components/MachineDetailPage.tsx

@@ -34,7 +34,7 @@ export class MachineDetailPage extends qreact.Component {
         for (let serviceId of serviceList) {
             let serviceConfig = controller.getServiceConfig(serviceId);
             if (!serviceConfig?.parameters.deploy) continue;
-            if (serviceConfig && serviceConfig.machineIds.includes(selectedMachineId)) {
+            if (serviceConfig && (serviceConfig.parameters.machineIds || []).includes(selectedMachineId)) {
                 relevantServiceConfigs.set(serviceId, serviceConfig);
             }
         }