querysub 0.268.0 → 0.269.0

package/package.json

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

package/src/4-deploy/edgeBootstrap.ts

@@ -247,11 +247,17 @@ async function edgeNodeFunction(config: {
     progressUI.setMessage("Finding available server...");
     let retryCount = 0;
     while (true) {
+        let cached = !!cachedConfig;
         try {
             let booted = await tryToBoot();
             if (booted) break;
         } catch (e) {
             console.error(e);
+            // If it's a cached failure, it might be that the cache is out of date, so rerun immediately without waiting or an error message.
+            if (cached) {
+                cachedConfig = undefined;
+                continue;
+            }
         }
         retryCount++;
         progressUI.setMessage(`No available servers, retried ${retryCount++} times`);
@@ -290,6 +296,7 @@ async function edgeNodeFunction(config: {
     }
     async function getEdgeNodeConfig(): Promise<EdgeNodeConfig> {
         let edgeIndex = cachedConfig || await (await fetch(config.edgeNodeConfigURL)).json() as EdgeNodesIndex;
+        cachedConfig = undefined;
 
         edgeIndex.edgeNodes.sort((a, b) => -(a.bootTime - b.bootTime));
         // Filter out duplicate hostnames (taking the max bootTime). We can't have multiple services using the same port, so duplicates are DEFINITELY dead. This fixes some issues with accessing old services, and generally makes reading the logs easier.
@@ -300,7 +307,6 @@ async function edgeNodeFunction(config: {
             return true;
         });
 
-        cachedConfig = undefined;
         let liveHashForced = false;
         if (Date.now() < liveHashOverrideExpiryTime) {
             liveHashForced = true;

package/src/deployManager/spec.txt

@@ -1,7 +1,7 @@
-8) Fix deploy user notification issue, where the refresh button doesn't work?
-    - For application level updates
-    - Just an application commit, then deploy the service, then the refresh button should show up, and work
+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?