sliftutils 1.7.100 → 1.7.102

package/index.d.ts

@@ -3368,6 +3368,8 @@ declare module "sliftutils/storage/remoteStorage/blobStore" {
             /** Asks the client whose request created this store what routing config it intended for our name. Only used when init finds NO configuration in our folder: a store only ever exists because a config names it, so the requester has that config - asking for it lazily is the same information as passing the config on every call, without the per-call kilobytes. */
             requestRoutingConfig?: (() => Promise<RemoteConfig | undefined>) | undefined;
             onWriteCounted?: ((kind: "original" | "flushed", bytes: number) => void) | undefined;
+            /** A synchronization transfer: "sync get" is bytes pulled off a source (the backblaze download bill), "sync set" is bytes pushed to one. Injected because sync traffic never passes through the API controller, so nothing else can count it. */
+            onSyncTransfer?: ((operation: "sync get" | "sync set", path: string, bytes: number) => void) | undefined;
             resolveSourceUrl?: ((url: string) => IArchives) | undefined;
         } | undefined);
         /** This store's folder, unwrapped: the same bytes slot 0 serves, but reached without its write delay. Used for the two things that cannot go through a buffered source - reading our own routing config before we have any sources, and streaming a large upload that must not sit in memory. */
@@ -3554,6 +3556,8 @@ declare module "sliftutils/storage/remoteStorage/blobStore" {
         setIndexDeleted(key: string, writeTime: number): boolean;
         /** Forgets a key entirely, tombstone included. NOT a deletion: it says nothing happened to the file, only that we no longer know anything about it - for an entry whose holder turned out not to have it, and for a tombstone old enough that everyone has heard. */
         purgeIndexEntry(key: string): void;
+        /** Counts a synchronization transfer in the server's access statistics (see getStore's wiring): "sync get" for bytes pulled off a source, "sync set" for bytes pushed to one. */
+        noteSyncTransfer(operation: "sync get" | "sync set", path: string, bytes: number): void;
         /**
          * Every write, however it is stamped, has to be one we are actually meant to hold - because the
          * alternative is not a smaller problem, it is a silent one. A write that lands on a store that

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "sliftutils",
-    "version": "1.7.100",
+    "version": "1.7.102",
     "main": "index.js",
     "license": "MIT",
     "files": [

package/storage/remoteStorage/blobStore.d.ts

@@ -62,6 +62,8 @@ export declare class BlobStore {
         /** Asks the client whose request created this store what routing config it intended for our name. Only used when init finds NO configuration in our folder: a store only ever exists because a config names it, so the requester has that config - asking for it lazily is the same information as passing the config on every call, without the per-call kilobytes. */
         requestRoutingConfig?: (() => Promise<RemoteConfig | undefined>) | undefined;
         onWriteCounted?: ((kind: "original" | "flushed", bytes: number) => void) | undefined;
+        /** A synchronization transfer: "sync get" is bytes pulled off a source (the backblaze download bill), "sync set" is bytes pushed to one. Injected because sync traffic never passes through the API controller, so nothing else can count it. */
+        onSyncTransfer?: ((operation: "sync get" | "sync set", path: string, bytes: number) => void) | undefined;
         resolveSourceUrl?: ((url: string) => IArchives) | undefined;
     } | undefined);
     /** This store's folder, unwrapped: the same bytes slot 0 serves, but reached without its write delay. Used for the two things that cannot go through a buffered source - reading our own routing config before we have any sources, and streaming a large upload that must not sit in memory. */
@@ -248,6 +250,8 @@ export declare class BlobStore {
     setIndexDeleted(key: string, writeTime: number): boolean;
     /** Forgets a key entirely, tombstone included. NOT a deletion: it says nothing happened to the file, only that we no longer know anything about it - for an entry whose holder turned out not to have it, and for a tombstone old enough that everyone has heard. */
     purgeIndexEntry(key: string): void;
+    /** Counts a synchronization transfer in the server's access statistics (see getStore's wiring): "sync get" for bytes pulled off a source, "sync set" for bytes pushed to one. */
+    noteSyncTransfer(operation: "sync get" | "sync set", path: string, bytes: number): void;
     /**
      * Every write, however it is stamped, has to be one we are actually meant to hold - because the
      * alternative is not a smaller problem, it is a silent one. A write that lands on a store that

package/storage/remoteStorage/blobStore.ts

@@ -106,6 +106,8 @@ export class BlobStore {
             requestRoutingConfig?: () => Promise<RemoteConfig | undefined>;
             // Every accepted write ("original") and every write that actually reached the sources ("flushed"). Fast writes coalesce, so the two counts differ.
             onWriteCounted?: (kind: "original" | "flushed", bytes: number) => void;
+            /** A synchronization transfer: "sync get" is bytes pulled off a source (the backblaze download bill), "sync set" is bytes pushed to one. Injected because sync traffic never passes through the API controller, so nothing else can count it. */
+            onSyncTransfer?: (operation: "sync get" | "sync set", path: string, bytes: number) => void;
             // Resolves a persisted source URL (see ArchivesSource.url) to a cached IArchives, so entries whose holder is no longer configured can still be read
             resolveSourceUrl?: (url: string) => IArchives;
         }
@@ -804,6 +806,11 @@ export class BlobStore {
         this.index.purge(key);
     }
 
+    /** Counts a synchronization transfer in the server's access statistics (see getStore's wiring): "sync get" for bytes pulled off a source, "sync set" for bytes pushed to one. */
+    public noteSyncTransfer(operation: "sync get" | "sync set", path: string, bytes: number): void {
+        this.config?.onSyncTransfer?.(operation, path, bytes);
+    }
+
     // ── validation (from this store's own routing entries) ──
 
     /**

package/storage/remoteStorage/createArchives.ts

@@ -313,7 +313,7 @@ export class ArchivesChain implements IArchives {
         await this.state.refreshActiveConfig();
     }
 
-    private async request<T>(config: { apiOnly?: boolean; write?: boolean; route?: number; noFallbacks?: boolean; fallbacks?: boolean; fast?: boolean; timeout?: SmartTimeout }, run: (archives: IArchives, sourceUrl: string) => Promise<T>): Promise<T> {
+    private async request<T>(config: { apiOnly?: boolean; write?: boolean; route?: number; noFallbacks?: boolean; fallbacks?: boolean; retries?: number; fast?: boolean; timeout?: SmartTimeout }, run: (archives: IArchives, sourceUrl: string) => Promise<T>): Promise<T> {
         let state = await this.state.getState();
         return await this.run(state, config, run);
     }