cry-synced-db-client 0.1.185 → 0.1.186
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +32 -0
- package/dist/index.js +3 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,37 @@
|
|
|
1
1
|
# Versions
|
|
2
2
|
|
|
3
|
+
## 0.1.186 (2026-05-15)
|
|
4
|
+
|
|
5
|
+
### `WakeSyncManager` silences expected wake-time `timeout` errors
|
|
6
|
+
|
|
7
|
+
After sleep → wake the network is typically still reconnecting, so the
|
|
8
|
+
sync triggered by `WakeSyncManager` frequently times out on the first
|
|
9
|
+
attempt. The self-healing scheduler (auto-sync timer + reconnect timer
|
|
10
|
+
from `0.1.141`) retries the next tick and recovers without operator
|
|
11
|
+
attention — so logging the wake-time timeout was pure noise.
|
|
12
|
+
|
|
13
|
+
```ts
|
|
14
|
+
// Before: every timeout fired through networkError (info/error per online state).
|
|
15
|
+
this.deps.sync(`wake-sync:${trigger}`).catch((err) => {
|
|
16
|
+
networkError(`[WakeSync] Wake sync (${trigger}) failed:`, err);
|
|
17
|
+
});
|
|
18
|
+
|
|
19
|
+
// After: timeouts dropped silently; all other failures still routed
|
|
20
|
+
// through networkError for severity demotion.
|
|
21
|
+
this.deps.sync(`wake-sync:${trigger}`).catch((err: unknown) => {
|
|
22
|
+
const msg = (err as { message?: string } | null)?.message ?? "";
|
|
23
|
+
if (/timeout/i.test(msg)) return;
|
|
24
|
+
networkError(`[WakeSync] Wake sync (${trigger}) failed:`, err);
|
|
25
|
+
});
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
Match is case-insensitive on the error `message` substring `timeout` —
|
|
29
|
+
covers `RestProxy` timeout (`"REST call <op> timed out after Nms"`),
|
|
30
|
+
worker-call timeout, and the streaming-sync abort path. Non-timeout
|
|
31
|
+
failures (server 5xx, auth, msgpack parse) keep their existing
|
|
32
|
+
severity. Wake events that succeed continue to fire `onWakeSync` and
|
|
33
|
+
hydrate the local cache as before.
|
|
34
|
+
|
|
3
35
|
## 0.1.185 (2026-05-14)
|
|
4
36
|
|
|
5
37
|
### Fix: server-wins rebase resolves dirty-merge path conflicts (`sestevki`)
|
package/dist/index.js
CHANGED
|
@@ -4304,6 +4304,9 @@ var WakeSyncManager = class {
|
|
|
4304
4304
|
}
|
|
4305
4305
|
}
|
|
4306
4306
|
this.deps.sync(`wake-sync:${trigger}`).catch((err) => {
|
|
4307
|
+
var _a;
|
|
4308
|
+
const msg = (_a = err == null ? void 0 : err.message) != null ? _a : "";
|
|
4309
|
+
if (/timeout/i.test(msg)) return;
|
|
4307
4310
|
networkError(`[WakeSync] Wake sync (${trigger}) failed:`, err);
|
|
4308
4311
|
});
|
|
4309
4312
|
}, this.debounceMs);
|