querysub 0.302.0 → 0.303.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1469,6 +1469,7 @@ export class PathValueProxyWatcher {
|
|
|
1469
1469
|
);
|
|
1470
1470
|
let newReadCheck = !!value.isTransparent;
|
|
1471
1471
|
if (oldReadCheck !== newReadCheck) {
|
|
1472
|
+
console.error(`Old read check ${oldReadCheck} !== newReadCheck ${newReadCheck} for ${value.path}, canGCValue: ${value.canGCValue}, isTransparent: ${value.isTransparent}`);
|
|
1472
1473
|
// IMPORTANT! IF WE HIT THIS ASSERT, DEBUG IT RIGHT NOW!
|
|
1473
1474
|
// - I updated the read check to use isTransparent. BUT... I'm not sure
|
|
1474
1475
|
// this is correct. This WILL break if we add any new isTransparent values,
|
|
@@ -367,6 +367,14 @@ const runScreenCommand = measureWrap(async function runScreenCommand(config: {
|
|
|
367
367
|
} else {
|
|
368
368
|
console.log(red(`No nodeId file found for ${screenName}, not triggering rolling update notification`));
|
|
369
369
|
}
|
|
370
|
+
// Stop the pipe-pane, and delete the pipe file
|
|
371
|
+
try {
|
|
372
|
+
await runPromise(`${prefix}tmux pipe-pane -O -t ${screenName}`);
|
|
373
|
+
await fs.promises.unlink(os.homedir() + "/" + SERVICE_FOLDER + screenName + "/pipe.txt");
|
|
374
|
+
} catch (e: any) {
|
|
375
|
+
console.warn(`Error stopping pipe-pane for ${screenName}: ${e.stack}`);
|
|
376
|
+
}
|
|
377
|
+
|
|
370
378
|
let rollingScreenName = screenName + "-rolling" + SCREEN_SUFFIX;
|
|
371
379
|
console.log(green(`Renaming screen ${screenName} to ${rollingScreenName} for rolling interval ${config.rollingWindow} at ${new Date().toLocaleString()}`));
|
|
372
380
|
await runPromise(`${prefix}tmux rename-session -t ${screenName} ${rollingScreenName}`);
|
|
@@ -1,5 +1,11 @@
|
|
|
1
|
+
TODO: It seems like every other time it fails to reload?
|
|
2
|
+
|
|
3
|
+
Uh... we get a failure in commitWrites, and then we never receive the path values we need?
|
|
4
|
+
- Although we only don't receive the values we need once, so... maybe the failed check is okay?
|
|
5
|
+
|
|
1
6
|
1) Verify clientside notifications work when we rolling update cyoa
|
|
2
7
|
2) Verify edge nodes are removed when we rolling update cyoa
|
|
8
|
+
- Eh... it removes most of the time?
|
|
3
9
|
3) Update cyoa rolling time back to 4 hours
|
|
4
10
|
|
|
5
11
|
1) Auto restart if the connect to the cyoa server is down, after 30 seconds, instead of just infinitely erroring out.
|