Claude c863812b1e fix(relayBench): stop the corpus tools silently serving/keeping wrong events ...

Two benchmark-integrity bugs that could invalidate sync numbers while a run
reports success:

- CorpusServerMain keyed its serve-existing decision only on port + row
  count, so re-running a port with a different corpus/maxCount, or after a
  load crashed mid-way, silently served a stale/partial DB. Gate reuse on a
  completion sentinel keyed on corpus identity (path + byte length) and
  maxCount, written only after a full load; on any mismatch the prior DB is
  dropped and reloaded.
- CorpusDownloader treated CLOSED identically to EOSE, so a relay ending a
  sub early (rate-limit/policy) after sending a partial page advanced the
  cursor past the unsent tail — silent corpus loss. Treat CLOSED as a soft
  failure (null → reconnect and retry the same cursor; the id dedup set
  absorbs the re-fetch), distinct from EOSE which means the page is
  complete.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EZeWww5TJnzBZKPoc6mvU

2026-07-05 04:55:37 +00:00

..

main/kotlin/com/vitorpamplona/relaybench

fix(relayBench): stop the corpus tools silently serving/keeping wrong events

2026-07-05 04:55:37 +00:00

test/kotlin/com/vitorpamplona/relaybench

feat: add relayBench — head-to-head relay benchmark (geode vs strfry vs any)

2026-07-03 18:37:16 +00:00