@cloudbitmaps/roaring 0.18.3 → 0.19.1

package/dist/testing/conformance.d.ts

@@ -15,7 +15,7 @@ export declare function storageChunkSourceConformance(label: string, makeSource:
     bitmap: SafeBitmap;
 }>) => Promise<StorageChunkSource>): void;
 /** The storage-driver cases {@link storageDriverConformance} runs; an emulator that cannot model one skips it by name. */
-export type StorageDriverCase = 'write-once round trip' | 'collision' | 'collision on a large upload' | 'missing object' | 'out-of-range read' | 'tail size' | 'idempotent delete' | 'delete of an absent key beside its neighbours' | 'list read-after-delete';
+export type StorageDriverCase = 'write-once round trip' | 'collision' | 'collision on a large upload' | 'missing object' | 'out-of-range read' | 'tail size' | 'idempotent delete' | 'delete of an absent key beside its neighbours' | 'list read-after-delete' | 'names and namespaces kept apart' | 'generations by number' | 'failed write' | 'missing location' | 'list across pages';
 /**
  * Contract tests for an {@link IStorageDriver} — the contract its doc comment lists: write-once with
  * `WriteConflictError` on a collision, `NotFoundError` for a missing object, `ValidationError` for an out-of-range
@@ -34,13 +34,40 @@ export declare function storageDriverConformance(label: string, makeDriver: () =
      * sent on a different request than a small object's. Omitted, the case does not run.
      */
     readonly largeBytes?: number;
+    /**
+     * A driver over a bucket or container that does not exist, built fresh on each call. The `missing location` case
+     * holds it to failing a range read, a tail read, a delete and a listing with an error that is neither
+     * `NotFoundError` nor `TransientError`: read as an absence, a misnamed or deleted bucket answers every read of the
+     * store as an empty segment. Omitted, the case does not run.
+     */
+    readonly missingLocation?: () => IStorageDriver;
+    /**
+     * How many generations the `list across pages` case writes and lists back. Pass more than one listing page of the
+     * driver under test (S3 and GCS list 1,000 a page, Azure Blob 5,000, a test double what it is built with), so a
+     * driver that drops its continuation token fails. Omitted, the case does not run.
+     */
+    readonly pagedListSize?: number;
 }): void;
 /**
  * Contract tests for an {@link IRegistryDriver}. `makeDriver` MUST return a fresh, empty, isolated driver on
  * each call. The OCC contract (create / token-fenced CAS / ABA) plus the registry's record semantics (forward
  * currentGen, status, clearable keyId, discovery).
  */
-export declare function registryConformance(label: string, makeDriver: () => IRegistryDriver): void;
+export declare function registryConformance(label: string, makeDriver: () => IRegistryDriver, options?: {
+    /**
+     * A driver over a bucket or container that does not exist, built fresh on each call. The `missing location` case
+     * holds it to failing a read, a listing and a create with an error that is neither `NotFoundError` nor
+     * `TransientError`, and never answering a read with `null`: read as an absent row, a misnamed or deleted bucket
+     * answers every segment as one with no generation. Omitted, the case does not run.
+     */
+    readonly missingLocation?: () => IRegistryDriver;
+    /**
+     * How many rows the `list across pages` case creates and lists back. Pass more than one listing page of the driver
+     * under test (S3 and GCS list 1,000 a page, Azure Blob 5,000, a test double what it is built with), so a driver
+     * that drops its continuation token fails. Omitted, the case does not run.
+     */
+    readonly pagedListSize?: number;
+}): void;
 /**
  * Contract tests for an {@link IRegistryDriver} under **concurrent writers** — `makeDrivers` MUST return two
  * independent driver instances over the **same** backing store, as two processes would see it.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cloudbitmaps/roaring",
-  "version": "0.18.3",
+  "version": "0.19.1",
   "description": "Distributed, cloud-native Roaring Bitmaps — query and intersect billion-scale integer sets straight out of object storage, from a bounded RAM cache over immutable objects in your own bucket, at a fraction of an always-on cache.",
   "keywords": [
     "roaring",
@@ -65,7 +65,7 @@
   },
   "dependencies": {
     "roaring": "2.7.0",
-    "@cloudbitmaps/core": "^0.18.3"
+    "@cloudbitmaps/core": "^0.19.1"
   },
   "devDependencies": {
     "@types/node": "^22.0.0",