@serfab/quereus-plugin-sereus 1.5.0 → 1.7.0
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@serfab/quereus-plugin-sereus",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.7.0",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"description": "Quereus plugin that connects to a Sereus strand for SQL access",
|
|
6
6
|
"main": "dist/index.js",
|
|
@@ -67,12 +67,12 @@
|
|
|
67
67
|
"@libp2p/circuit-relay-v2": "^4.1.3",
|
|
68
68
|
"@libp2p/interface": "^3.1.0",
|
|
69
69
|
"@libp2p/websockets": "^10.1.3",
|
|
70
|
-
"@optimystic/db-core": "^1.
|
|
71
|
-
"@optimystic/db-p2p": "^1.
|
|
72
|
-
"@optimystic/db-p2p-storage-fs": "^1.
|
|
73
|
-
"@optimystic/db-p2p-storage-web": "^1.
|
|
74
|
-
"@optimystic/quereus-plugin-crypto": "^1.
|
|
75
|
-
"@optimystic/quereus-plugin-optimystic": "^1.
|
|
70
|
+
"@optimystic/db-core": "^1.7.0",
|
|
71
|
+
"@optimystic/db-p2p": "^1.7.0",
|
|
72
|
+
"@optimystic/db-p2p-storage-fs": "^1.7.0",
|
|
73
|
+
"@optimystic/db-p2p-storage-web": "^1.7.0",
|
|
74
|
+
"@optimystic/quereus-plugin-crypto": "^1.7.0",
|
|
75
|
+
"@optimystic/quereus-plugin-optimystic": "^1.7.0",
|
|
76
76
|
"@quereus/quereus": "^4.20.0",
|
|
77
77
|
"debug": "^4.4.3"
|
|
78
78
|
},
|
package/src/cluster-size.ts
CHANGED
|
@@ -43,9 +43,9 @@ export const MIN_CLUSTER_SIZE = 2;
|
|
|
43
43
|
* **What it costs**, in the terms Optimystic's own field doc uses: a peer that is truly gone
|
|
44
44
|
* now holds a read of a block missing locally for up to 5 s before the read is declined
|
|
45
45
|
* instead of 1 s. A joining machine's first sync runs several such consults, so it is the cost
|
|
46
|
-
* that binds — and the first-sync band measured at BOTH deadlines, against the
|
|
47
|
-
*
|
|
48
|
-
* `strand-first-sync-gate.ts`. At 5000 against the 30 s budget that preceded
|
|
46
|
+
* that binds — and the first-sync band measured at BOTH deadlines, against the budget it has
|
|
47
|
+
* to fit, is recorded once, on `DEFAULT_STRAND_FIRST_SYNC_TIMEOUT_MS` in cadre-core's
|
|
48
|
+
* `strand-first-sync-gate.ts`. At 5000 against the 30 s budget that preceded it, this change
|
|
49
49
|
* would have turned a slow-but-working join into the very `StrandAwaitingFirstSyncError` the
|
|
50
50
|
* report named. 3000 is the fallback if that margin ever goes — still 1.7x the reported round
|
|
51
51
|
* trip, and a doomed consult costs 40% less.
|
|
@@ -74,10 +74,11 @@ export const MIN_CLUSTER_SIZE = 2;
|
|
|
74
74
|
* cadre-core's `NetworkConfig.cohortQueryTimeoutMs`, threaded to {@link controlClusterPolicy}
|
|
75
75
|
* and {@link strandClusterPolicy}.
|
|
76
76
|
*
|
|
77
|
-
* NOTE: this number and the first-sync budget are coupled
|
|
78
|
-
*
|
|
79
|
-
* first sync grows more collections than the two-table
|
|
80
|
-
* `DEFAULT_STRAND_FIRST_SYNC_TIMEOUT_MS` carries the result and
|
|
77
|
+
* NOTE: this number and the first-sync budget are coupled; the margin between that budget and
|
|
78
|
+
* the slowest first sync measured is stated on it. Re-measure the first-sync band before raising
|
|
79
|
+
* this again, or when a deployment's first sync grows more collections than the two-table
|
|
80
|
+
* scenario measured above — `DEFAULT_STRAND_FIRST_SYNC_TIMEOUT_MS` carries the result and
|
|
81
|
+
* `docs/testing.md` the recipe.
|
|
81
82
|
* Nothing warns when the margin goes; the symptom is `StrandAwaitingFirstSyncError` on a join
|
|
82
83
|
* that was progressing normally, which is the failure this pair of numbers exists to end.
|
|
83
84
|
*/
|