orez-sync-cf-host 0.16.1 → 0.16.2

package/dist/host.js

@@ -1293,7 +1293,7 @@ export function createSyncDurableObject(config) {
                         // Zero registry, synchronously: patch application order is
                         // arrival order by construction, with no cross-request await
                         // between resolution and the engine transaction.
-                        const patch = resolveQueryPatch(queries.patch, config.queries, claims, transformVersion, requestError);
+                        const patch = resolveQueryPatch(queries.patch, config.queries, claims, transformVersion, requestError, config.tolerateUnknownQueries === true);
                         body = { ...body, queries: { ...queries, patch } };
                     }
                     body = { ...body, _serverQueryTransformVersion: transformVersion };

package/dist/query-patch.d.ts

@@ -14,8 +14,21 @@ import type { AnyQueryRegistry } from '@rocicorp/zero';
  * `asQueryInternals`, whose instance-tag check fails whenever the app's
  * registry and this host resolve different copies of the zero module.
  *
- * A resolution error fails the whole patch (the pull is refused as one unit),
- * but the refusal names the query it came from, so a client that registers
- * one unknown query alongside nine good ones is told which one is unknown.
+ * By default a name the registry does not contain fails the whole patch (the
+ * pull is refused as one unit) and the refusal names the query it came from, so
+ * a client that registers one unknown query alongside nine good ones is told
+ * which one is unknown. Where client and server ship together that is the right
+ * answer: an unknown name means the registry was not regenerated, and a loud
+ * failure is how the developer finds out.
+ *
+ * A host that serves independently shipped clients sets
+ * `tolerateUnknownQueries`. A native binary is always older than the server it
+ * talks to, so it can ask for a query since renamed or removed; that is version
+ * skew rather than a fault. Under the flag the unknown put is dropped and the
+ * rest of the patch resolves, leaving the client without rows for that one
+ * query instead of unable to sync anything at all.
+ *
+ * A query that IS registered but fails to build is a real fault in the app's
+ * own code either way, so it always fails the whole patch and names the query.
  */
-export declare function resolveQueryPatch(patch: readonly unknown[], queries: AnyQueryRegistry, context: unknown, transformVersion: number, fail: (message: string) => Error): unknown[];
+export declare function resolveQueryPatch(patch: readonly unknown[], queries: AnyQueryRegistry, context: unknown, transformVersion: number, fail: (message: string) => Error, tolerateUnknownQueries?: boolean): unknown[];

package/dist/query-patch.js

@@ -15,18 +15,35 @@ const NAME_SEPARATOR = /[.|]/;
  * `asQueryInternals`, whose instance-tag check fails whenever the app's
  * registry and this host resolve different copies of the zero module.
  *
- * A resolution error fails the whole patch (the pull is refused as one unit),
- * but the refusal names the query it came from, so a client that registers
- * one unknown query alongside nine good ones is told which one is unknown.
+ * By default a name the registry does not contain fails the whole patch (the
+ * pull is refused as one unit) and the refusal names the query it came from, so
+ * a client that registers one unknown query alongside nine good ones is told
+ * which one is unknown. Where client and server ship together that is the right
+ * answer: an unknown name means the registry was not regenerated, and a loud
+ * failure is how the developer finds out.
+ *
+ * A host that serves independently shipped clients sets
+ * `tolerateUnknownQueries`. A native binary is always older than the server it
+ * talks to, so it can ask for a query since renamed or removed; that is version
+ * skew rather than a fault. Under the flag the unknown put is dropped and the
+ * rest of the patch resolves, leaving the client without rows for that one
+ * query instead of unable to sync anything at all.
+ *
+ * A query that IS registered but fails to build is a real fault in the app's
+ * own code either way, so it always fails the whole patch and names the query.
  */
-export function resolveQueryPatch(patch, queries, context, transformVersion, fail) {
-    const result = [...patch];
-    patch.forEach((operation, index) => {
-        if (!operation || typeof operation !== 'object')
-            return;
+export function resolveQueryPatch(patch, queries, context, transformVersion, fail, tolerateUnknownQueries = false) {
+    const result = [];
+    for (const operation of patch) {
+        if (!operation || typeof operation !== 'object') {
+            result.push(operation);
+            continue;
+        }
         const op = operation;
-        if (op.op !== 'put')
-            return;
+        if (op.op !== 'put') {
+            result.push(operation);
+            continue;
+        }
         if (typeof op.name !== 'string') {
             throw fail('query put requires a server-resolved named query');
         }
@@ -41,7 +58,11 @@ export function resolveQueryPatch(patch, queries, context, transformVersion, fai
         }
         const custom = node;
         if (!custom || typeof custom.fn !== 'function') {
-            throw fail(`unknown or unsupported named query: ${op.name}`);
+            if (!tolerateUnknownQueries)
+                throw fail(`unknown or unsupported named query: ${op.name}`);
+            // version skew: drop this query and keep syncing the rest.
+            console.warn(`orez: dropping unknown named query from pull: ${op.name}`);
+            continue;
         }
         let ast;
         try {
@@ -56,14 +77,14 @@ export function resolveQueryPatch(patch, queries, context, transformVersion, fai
         }
         catch (error) {
             const detail = error instanceof Error ? error.message : String(error);
-            throw fail(`unknown or unsupported named query: ${op.name}: ${detail}`);
+            throw fail(`named query failed to build: ${op.name}: ${detail}`);
         }
-        result[index] = {
+        result.push({
             op: 'put',
             hash: op.hash,
             ast,
             transformVersion,
-        };
-    });
+        });
+    }
     return result;
 }

package/dist/types.d.ts

@@ -106,6 +106,19 @@ export type SyncHostConfig<Env extends SyncHostEnv = SyncHostEnv, S extends Sche
      * query context. There is no app endpoint to call and nothing else to wire.
      */
     queries: AnyQueryRegistry;
+    /**
+     * Drop a desired query whose name is not in `queries` instead of refusing the
+     * whole pull. Off by default, because where the client ships with the server
+     * an unknown name means the registry was not regenerated and the request
+     * error is how that gets noticed.
+     *
+     * Set it when the host serves clients that ship on their own schedule, such
+     * as a native app in an app store. Those clients are routinely older than the
+     * server and will ask for queries that have since been renamed or removed;
+     * without this the pull is refused as one unit and an app one feature out of
+     * date cannot sync anything at all.
+     */
+    tolerateUnknownQueries?: boolean;
     /**
      * Streaming fields for this namespace: which columns may carry a live,
      * uncommitted value, and their publish mode and rate bounds.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "orez-sync-cf-host",
-  "version": "0.16.1",
+  "version": "0.16.2",
   "description": "Internal orez Cloudflare sync host. Do not import directly: consumers use orez-lite/cloudflare/sync.",
   "type": "module",
   "exports": {
@@ -48,7 +48,7 @@
     "bundle": "bun run build:dist && wrangler deploy --dry-run --outdir .wrangler/bundle",
     "measure": "bun run build:dist && bun measure.mjs",
     "test": "bun run test:config && bun run test:query-compiler && bun run test:package && bun run test:platform && bun run test:integration && bun run test:large-data && bun run test:ingest && bun run test:restart",
-    "test:config": "bun test config.test.mjs write-safeguards.test.mjs transaction-query.test.mjs upstream-response.test.mjs serving-lag.test.mjs",
+    "test:config": "bun test config.test.mjs query-patch.test.mjs write-safeguards.test.mjs transaction-query.test.mjs upstream-response.test.mjs serving-lag.test.mjs",
     "test:integration": "bun run build:dist && bun integration-test.mjs",
     "test:ingest": "bun run build:dist && bun ingest-test.mjs",
     "test:package": "bun run build:dist && node package-runtime-test.mjs",
@@ -60,7 +60,7 @@
   },
   "dependencies": {
     "@opentelemetry/api": "^1.9.0",
-    "orez-sync-executor": "0.16.1"
+    "orez-sync-executor": "0.16.2"
   },
   "devDependencies": {
     "@cloudflare/workers-types": "4.20260617.1",