reeflog-client 0.7.23 → 0.7.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/README.md +15 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -5,7 +5,7 @@ they did to account balances for selected programs into a cursor-addressed
|
|
|
5
5
|
append-only log, so a consumer resumes without gaps after a crash,
|
|
6
6
|
disconnect, or reorg.
|
|
7
7
|
|
|
8
|
-
**Status: v0.7.
|
|
8
|
+
**Status: v0.7.24 shipped (2026-11-13), v0 working.** Live against mainnet-beta: see *Measured results* below. Install the binary without a Rust toolchain: `npm install reeflog-client` then `import { bootstrap } from 'reeflog-client'; await bootstrap()` (downloads the prebuilt release archive and verifies its sha256; the archive digests are `6cea050d…` linux / `d3cbe390…` macos, both equal what the release API publishes). The same install from the tagged release: `npm install github:auroraxo/reeflog#v0.7.24`. Or from source: `cargo install --git https://github.com/auroraxo/reeflog --tag v0.7.24`. The full event envelope (logs, balances, instructions, account list with owners, the bytes each account held, and the authority each token account had at the moment of the event), the Node client (see *The Node client*), webhook fan-out, a dead-letter queue, and archive backfill ship in this tree; Yellowstone as a second transport does not.
|
|
9
9
|
|
|
10
10
|
## The idea
|
|
11
11
|
|
|
@@ -941,6 +941,19 @@ reeflog start --db reeflog.db --webhook-config webhooks.json --webhook-every 5
|
|
|
941
941
|
`X-Reeflog-Event-Id` sees the same event it rejected (or missed), not a
|
|
942
942
|
new one. A replay that is refused again stays in the queue and exits 3;
|
|
943
943
|
nothing is ever dropped.
|
|
944
|
+
8. **A failure that ended stops being reported.** `webhook status` carries
|
|
945
|
+
`last_error` — the reason the target's MOST RECENT delivery pass stopped.
|
|
946
|
+
Since v0.7.24 that reason belongs to the pass that produced it: the next
|
|
947
|
+
pass for that target clears it and re-sets it only if the pass stops
|
|
948
|
+
again. Measured on the published v0.7.23 asset
|
|
949
|
+
(`research/webhook-stale-error-published-v0723-2026-11-13.json`, verdict
|
|
950
|
+
`stale-error-verdict-present`): the endpoint refused once (`http 500`,
|
|
951
|
+
`push` exited 3), the next pass delivered everything and exited 0 — and
|
|
952
|
+
`webhook status` still said `http 500`. A monitoring caller that polls
|
|
953
|
+
the status alarmed forever on a failure that had ended, and an operator
|
|
954
|
+
repaired the same endpoint twice. A failure that still stands is
|
|
955
|
+
re-reported on every pass it still happens, so nothing is hidden: the
|
|
956
|
+
rule moves the verdict forward with the passes, it does not swallow it.
|
|
944
957
|
|
|
945
958
|
### Measured, against an independent receiver
|
|
946
959
|
|
|
@@ -1688,7 +1701,7 @@ contract, and a library's idea of the schema cannot drift from the daemon's.
|
|
|
1688
1701
|
|
|
1689
1702
|
```bash
|
|
1690
1703
|
npm install reeflog-client # the registry; this version, no Rust toolchain
|
|
1691
|
-
npm install github:auroraxo/reeflog#v0.7.
|
|
1704
|
+
npm install github:auroraxo/reeflog#v0.7.24 # the same client from the tagged release
|
|
1692
1705
|
```
|
|
1693
1706
|
|
|
1694
1707
|
The client needs the `reeflog` binary. `bootstrap()` gets it **without a
|
package/package.json
CHANGED