querysub 0.232.0 → 0.234.0

package/package.json

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

package/src/deployManager/machineApplyMainCode.ts

@@ -443,6 +443,7 @@ export async function machineApplyMain() {
     onServiceConfigChange(resyncServices);
 
     runInfinitePoll(timeInMinute, async () => {
+        console.log(magenta(`Quick outdated check at ${new Date().toISOString()}`));
         if (await quickIsOutdated()) {
             console.log(magenta("Likely outdated, resyncing now"));
             await resyncServices();

package/src/deployManager/spec.txt

@@ -1,8 +1,4 @@
-7) More graceful shutdown of services
-    - In some way communicate that we should shut down?
-    - ACTUALLY, we just ctrl+c, which... we might catch right now?
-        - So we might need to use ctrl+c multiple times, and callback to kill the service?
-    
+NOTE: Yarn 
 
 7.1) Better infinite poll support in shutdown
     - Stop all loops

package/src/diagnostics/periodic.ts

@@ -62,6 +62,7 @@ export async function shutdown() {
     process.exit();
 }
 
+// IMPORTANT! Yarn detaches the processes, so they keep running when you ctrl+c, even though the shell shows back up. We can fix this by using `node -r ./node_modules/typenode/index.js ./test.ts`. However, it's probably fine, as we still run the shutdown code, it's just that the manager doesn't know if we've shutdown or not.
 if (isNode()) {
     let lineBuffer = "";
     process.stdin.on("data", data => {