sliftutils 1.7.23 → 1.7.24

package/storage/remoteStorage/spec.md

@@ -46,4 +46,4 @@ Machines authenticate with their certs.ts identity (proving ownership of their m
 
     We look at the valid state windows and we make sure we never delay past the valid state window. In fact, if we are within five minutes of being invalid due to the valid state window, we flush the writes immediately. That way, when the next valid window starts running, the writes will be already on disk. 
 
-    We also do scans when we are coming up to the valid state window. If we are going to be the new valid state window, both before, a little bit after, and farther after. This helps the switch over be smoother so we get all of the trailing writes. These scans use our ability to ask for the changes since a certain time. We do the scan on the right write node. The write node is always the first available node.
+    We also do scans when we are coming up to the valid state window. If we are going to be the new valid state window, both before, a little bit after, and farther after. This helps the switch over be smoother so we get all of the trailing writes. These scans use our ability to ask for the changes since a certain time. We do the scan on the right write node. The write node is always the first node in order (with a valid state window and matching the route hash). Which might result in us having to scan multiple nodes if we require multiple nodes to fill the full route hash window. 

package/storage/remoteStorage/storageServerState.ts

@@ -692,7 +692,7 @@ class ArchivesLocalBucket implements IArchives {
     }
 
     public getDebugName() {
-        return `localBucket/${this.account}/${this.bucketName}`;
+        return `localBucket account ${this.account} bucket ${this.bucketName}`;
     }
     public async get(fileName: string, config?: { range?: { start: number; end: number } }): Promise<Buffer | undefined> {
         let result = await this.get2(fileName, config);