querysub 0.269.0 → 0.270.0

package/package.json

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

package/src/3-path-functions/pathFunctionLoader.ts

@@ -323,6 +323,7 @@ export function getSpecFromModule(module: NodeJS.Module): LoadFunctionSpec | und
 async function getModuleFromSpecBase(
     spec: LoadFunctionSpec
 ): Promise<NodeJS.Module> {
+    console.log(blue(`Loading module for ${JSON.stringify(spec)}`));
     // Register ourself as overlapping, to prevent ambient modules from being set in this way.
     registerSpec(module.filename, "overlapping");
 

package/src/4-querysub/Querysub.ts

@@ -801,6 +801,8 @@ export class Querysub {
             let existingRecords = await getRecords("A", getDomain());
             if (ip !== "127.0.0.1") {
                 let validRecords: string[] = [];
+                // Ignore ourself, we want OTHER records.
+                existingRecords = existingRecords.filter(x => x !== ip);
                 await Promise.all(existingRecords.map(async (record) => {
                     let isListening = await timeoutToUndefined(timeInSecond * 10, testTCPIsListening(record, 443));
                     if (isListening) {

package/src/deployManager/spec.txt

@@ -1,8 +1,3 @@
-Bug, if we refresh immediately after an update, we get into a state where we know we should be using a new hash, but the lookup for the hashes is cached, so we think the server doesn't exist,
-    - Hopefully it's just that we're using the cache we received from the server. If it's actually being cached in Cloudflare, that's annoying and I think we just need to fall back if we see the live hash has been updated recently. Although I don't think we're storing the timestamps so that's annoying. 
-
-7) verify manually refreshing removes the message
-
 8) Use a special service for the HTTP bootstrapper, and then have 2 others that are on other ports
     --bootstraponly is added, and should work?
 

package/src/library-components/SyncedController.ts

@@ -95,6 +95,8 @@ export function getSyncedController<T extends SocketRegistered>(
          */
         reads?: { [key in keyof T["nodes"][""]]?: string[]; };
         writes?: { [key in keyof T["nodes"][""]]?: string[]; };
+        // TODO: Add a flag to give timeouts, so values are automatically refreshed every once in a while, so pages don't get too stale?
+        //  - BUT with a "softRefresh", so we don't trigger a re-render, we only update it if it is accessed again!
     }
 ): {
     (nodeId: string): {