@spooky-sync/core 0.0.1-canary.372 → 0.0.1-canary.374

package/dist/index.js

@@ -569,9 +569,18 @@ const NETWORK_ERROR_PATTERNS = [
 * which would otherwise hold the outbox's serial lane forever.
 */
 const SP00KY_EVENT_POST_FAILED = /error while processing event _00_[^:\s]*: (?:there was an error processing a remote http request: (?:error sending request|5\d\d\b|408\b|429\b)|failed to lookup address information)/;
+/**
+* What the proxy in front of a database answers while the database is away: a
+* restart, or the seconds of a version upgrade. Over HTTP the SDK's error message
+* IS the response body, so these arrive as bare words, and an `application`
+* reading rolls the write back. Anchored: a statement can mention these words,
+* but SurrealDB never answers with nothing else.
+*/
+const PROXY_UNAVAILABLE = /^(?:bad gateway|service unavailable|gateway timeout|404 page not found)\s*$/;
 function classifySyncError(error) {
 	const message = error instanceof Error ? error.message.toLowerCase() : String(error).toLowerCase();
 	if (SP00KY_EVENT_POST_FAILED.test(message)) return "network";
+	if (PROXY_UNAVAILABLE.test(message)) return "network";
 	for (const pattern of NETWORK_ERROR_PATTERNS) if (message.includes(pattern)) return "network";
 	return "application";
 }
@@ -3650,8 +3659,8 @@ function trimHistory(history, cap) {
 
 //#endregion
 //#region src/modules/devtools/index.ts
-const CORE_VERSION = "0.0.1-canary.372";
-const WASM_VERSION = "0.0.1-canary.372";
+const CORE_VERSION = "0.0.1-canary.374";
+const WASM_VERSION = "0.0.1-canary.374";
 const SURREAL_VERSION = "3.1.0";
 var DevToolsService = class DevToolsService {
 	version = CORE_VERSION;
@@ -17609,7 +17618,7 @@ function createTabsCoordinator(config, s, host) {
 	return new TabsCoordinator({
 		tabId: s.tabId,
 		fingerprint: computeTabsFingerprint({
-			coreVersion: "0.0.1-canary.372",
+			coreVersion: "0.0.1-canary.374",
 			schemaHash: hash53(config.schemaSurql),
 			endpoint: config.database.endpoint ?? "",
 			namespace: config.database.namespace,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@spooky-sync/core",
-  "version": "0.0.1-canary.372",
+  "version": "0.0.1-canary.374",
   "type": "module",
   "sideEffects": false,
   "main": "./dist/index.js",
@@ -75,8 +75,8 @@
     }
   },
   "dependencies": {
-    "@spooky-sync/query-builder": "0.0.1-canary.372",
-    "@spooky-sync/ssp-wasm": "0.0.1-canary.372",
+    "@spooky-sync/query-builder": "0.0.1-canary.374",
+    "@spooky-sync/ssp-wasm": "0.0.1-canary.374",
     "@sqlite.org/sqlite-wasm": "3.53.0-build1",
     "@surrealdb/wasm": "^3.1.0",
     "@surrealdb/wasm-native": "^3.3.4",

package/src/utils/error-classification.test.ts

@@ -2,6 +2,17 @@ import { describe, it, expect } from 'vitest';
 import { classifySyncError, isRefusedSessionError } from './error-classification';
 
 describe('classifySyncError', () => {
+  it('classifies a proxy with no database behind it as network', () => {
+    // Over HTTP the SDK's message is the response body. These are Traefik's, while
+    // a database restarts or moves in a version upgrade; a rollback would lose the
+    // write.
+    for (const body of ['Bad Gateway', 'Service Unavailable', 'Gateway Timeout', '404 page not found\n']) {
+      expect(classifySyncError(new Error(body))).toBe('network');
+    }
+    // Only as the whole message: a statement's own error can use the words.
+    expect(classifySyncError(new Error('Thrown error: bad gateway to the partner API'))).toBe('application');
+  });
+
   it('classifies surreal ConnectionUnavailableError as network', () => {
     // Thrown synchronously by the WS engine's send() while the socket is down
     // but reconnect hasn't fired. Message contains "connected", not "connection".

package/src/utils/error-classification.ts

@@ -64,11 +64,21 @@ const NETWORK_ERROR_PATTERNS = [
 const SP00KY_EVENT_POST_FAILED =
   /error while processing event _00_[^:\s]*: (?:there was an error processing a remote http request: (?:error sending request|5\d\d\b|408\b|429\b)|failed to lookup address information)/;
 
+/**
+ * What the proxy in front of a database answers while the database is away: a
+ * restart, or the seconds of a version upgrade. Over HTTP the SDK's error message
+ * IS the response body, so these arrive as bare words, and an `application`
+ * reading rolls the write back. Anchored: a statement can mention these words,
+ * but SurrealDB never answers with nothing else.
+ */
+const PROXY_UNAVAILABLE = /^(?:bad gateway|service unavailable|gateway timeout|404 page not found)\s*$/;
+
 export function classifySyncError(error: unknown): 'network' | 'application' {
   const message =
     error instanceof Error ? error.message.toLowerCase() : String(error).toLowerCase();
 
   if (SP00KY_EVENT_POST_FAILED.test(message)) return 'network';
+  if (PROXY_UNAVAILABLE.test(message)) return 'network';
 
   for (const pattern of NETWORK_ERROR_PATTERNS) {
     if (message.includes(pattern)) {