@agentvault/agentvault 0.23.22 → 0.23.24
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/dist/channel.d.ts.map +1 -1
- package/dist/cli.js +59 -13
- package/dist/cli.js.map +4 -4
- package/dist/index.js +59 -13
- package/dist/index.js.map +4 -4
- package/dist/mls-commit-classify.d.ts +31 -0
- package/dist/mls-commit-classify.d.ts.map +1 -0
- package/openclaw.plugin.json +1 -1
- package/package.json +1 -1
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
/**
|
|
2
|
+
* #920: is a failed commit a FAILURE, or one we already applied?
|
|
3
|
+
*
|
|
4
|
+
* `_onCommitFailure` logged every rejected commit as
|
|
5
|
+
* `MLS commit failed (1/3) … ValidationError: Cannot process message, epoch too
|
|
6
|
+
* old`, with a retry counter and six stack frames. On a healthy room joining for
|
|
7
|
+
* the first time that line is a lie: the Welcome already advanced the agent to
|
|
8
|
+
* the new epoch, so the 0→1 commit pulled afterwards from `mls_delivery_queue`
|
|
9
|
+
* is one it has already applied.
|
|
10
|
+
*
|
|
11
|
+
* ⚠️ Read `_onCommitFailure`'s own comment before changing this. An earlier
|
|
12
|
+
* attempt classified by SUBSTRING-MATCHING the error text for "epoch" / "old" /
|
|
13
|
+
* "Validation", and `ValidationError: Desired gen in the past` contains
|
|
14
|
+
* "Validation" — so the loudest real production failure was filed as benign,
|
|
15
|
+
* 1,439 times on a single agent. That is why the code was deliberately left
|
|
16
|
+
* with "no classification. COUNT."
|
|
17
|
+
*
|
|
18
|
+
* This is not that. It never looks at the error text. It compares the two
|
|
19
|
+
* EPOCHS, which is protocol state rather than a message string:
|
|
20
|
+
*
|
|
21
|
+
* msg < group the group is already past it → already applied, benign
|
|
22
|
+
* msg >= group it should have applied → suspicious, count it
|
|
23
|
+
*
|
|
24
|
+
* The `>=` case is what preserves #474 and #629: a genuine divergence still
|
|
25
|
+
* counts toward the resync ladder. Anything unknown counts too, so an
|
|
26
|
+
* unparseable epoch can never silence a real failure — the failure mode of this
|
|
27
|
+
* function is noise, never silence.
|
|
28
|
+
*/
|
|
29
|
+
export type CommitFailureDisposition = "already-applied" | "count";
|
|
30
|
+
export declare function classifyCommitFailure(messageEpoch: unknown, groupEpoch: unknown): CommitFailureDisposition;
|
|
31
|
+
//# sourceMappingURL=mls-commit-classify.d.ts.map
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
{"version":3,"file":"mls-commit-classify.d.ts","sourceRoot":"","sources":["../src/mls-commit-classify.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,MAAM,MAAM,wBAAwB,GAAG,iBAAiB,GAAG,OAAO,CAAC;AA8BnE,wBAAgB,qBAAqB,CACnC,YAAY,EAAE,OAAO,EACrB,UAAU,EAAE,OAAO,GAClB,wBAAwB,CAO1B"}
|
package/openclaw.plugin.json
CHANGED