• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

cameri / nostream / 43976899489
78%
main: 79%

Build:
Build:
LAST BUILD BRANCH: rewrite/main
DEFAULT BRANCH: main
Ran 16 Nov 2026 11:16PM UTC
Jobs 2
Files 321
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

16 Nov 2026 11:10PM UTC coverage: 77.588% (+2.6%) from 75.031%
43976899489

push

github

web-flow
feat(storage): answer NIP-50 from an events_by_term index, parity-tested against the fixture (#1113)

Closes nothing by keyword: `base` is `rewrite/main`, not the
repository's default branch. #1109 is closed by hand after the merge.

**On a limited search, this store ranks by `(span, id)` where Postgres
keeps `created_at DESC`.** The set is the capture's; the order is not,
and it is the first thing to know about this change. Everything below is
the record of why, what it cost, and what it does not do.

NIP-50 search was refused on the LMDB path —
`StorageError::NotImplemented { module: "storage::lmdb::nip50_search" }`
— so `Filter::search` was a field a client could send and a store could
not answer. This adds a term index (`events_by_term`, the 30th named
database, key `term ‖ event_id`, empty values), a tokeniser shared by
the write and read paths, and a rank, so a searched `REQ`, `COUNT` and
reconciliation all answer from the same walk.

## What a reader should check first

The oracle is fixture entry 21, the search row the differential replay
had been excluding. It is replayed now:

```
base b42f833, parity arm edited:  exit 101  op 21 (events.find_by_filters) failed:
                                            not implemented in Phase 1 (job 005): storage::lmdb::nip50_search
head 06301de:                     LMDB_PARITY_COMPLETE replayed=114 excluded=48,50,112,115   43 passed
```

Entry 21 asks `search: "bitcoin lightning"` and the fixture records four
rows. The **token rule** (lowercase, then maximal alphanumeric runs,
every term a run of `content`) selects exactly those four; the capture's
in-memory **substring** rule selects a fifth (`f8ef9793…`,
`bitcoininveniice` / `#LightningNetwork`). The capture disagrees with
itself here — its SQL path uses `to_tsvector`/`ts_rank`, its memory path
substrings — and this store reproduces the SQL half's **predicate**, not
its ranker. The fixture's recorded order is `ts_rank`'s; `(min cover
span, event_id)` ... (continued)

4502 of 6342 branches covered (70.99%)

Branch coverage included in aggregate %.

9792 of 12081 relevant lines covered (81.05%)

759.03 hits per line

Jobs
ID Job ID Ran Files Coverage
1 Integration - 43976899489.1 16 Nov 2026 11:16PM UTC 321
33.0
GitHub Action Run
2 Unit - 43976899489.2 16 Nov 2026 11:17PM UTC 321
75.03
GitHub Action Run
Source Files on build 43976899489
  • Tree
  • List 321
  • Changed 236
  • Source Changed 0
  • Coverage Changed 236
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #43976899489
  • 8b785ceb on github
  • Prev Build on rewrite/main (#43976483504)
  • Next Build on rewrite/main (#44151931707)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc